-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
x86_64
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The performance profile got degraded during reboots
Version-Release number of selected component (if applicable):
4.20.0-rc.3
How reproducible:
Deploy MNO and apply Telco Performance profile - then reboot the nodes one by one
Steps to Reproduce:
1. Deploy an MNO cluster
2. Using ZTP, apply the Telco Performance Profile
3. Reboot every node on the cluster
Actual results:
Performance Profile is degraded reporting in "Vader" cluster:
"message": "could not get kubelet config key: error listing kubelet configs: rpc error: code = Unavailable desc = error reading from server: read tcp 10.17.96.120:39388->10.17.96.118:2379: read: connection reset by peer"
In another cluster "Orion", we got a different error:
"message": "Machine config pool worker Degraded Message: Failed to render configuration for pool worker: rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout.\n",
Expected results:
No performance profile degradation
Additional info:
Must-gather from the clusters:
https://drive.google.com/drive/folders/18mX-SkGXXQH-8lN-Syvb36jTqC_0HPET?usp=sharing
- relates to
-
OCPBUGS-62277 PerformanceProfile degraded after master nodes reboot in MNO
-
- Closed
-