Details
-
Bug
-
Resolution: Unresolved
-
Undefined
-
4.14.z
Description
When a PerformanceProfile is applied to a minor version upgrade and the worker mcp paused and then resumed at target version. The worker nodes go thru two reboots rendering multiple worker mc configs. With a default upgrade ( no PerformanceProfle) only the expected one reboot is observed.
Version-Release number of selected component (if applicable):
How reproducible
100%
Steps to Reproduce:
1.Create PerfProfile at pre upgrade 4.14 release
2.pause worker mcp
3.Upgrade to target version
4. Resume MCP
Actual results:
workers need 2 reboots
Expected results:
One reboot
Additional info:
apiVersion: performance.openshift.io/v2 kind: PerformanceProfile metadata: name: perf-profile-2m-worker spec: cpu: reserved: 0-3 isolated: 4-63 workloadHints: realTime: false hugepages: defaultHugepagesSize: "2M" pages: - size: "2M" count: 24000 node: 0 - size: "2M" count: 24000 node: 1 realTimeKernel: enabled: false numa: topologyPolicy: "best-effort" net: userLevelNetworking: false nodeSelector: node-role.kubernetes.io/worker: ""
Attachments
Issue Links
- is depended on by
-
-
- New
-