Description of problem: If MCP are paused while upgrading the cluster, the upgrade is not finishing and the machine-config cluster operator becomes degraded. Version-Release number of selected component (if applicable): All OCP 4.x How reproducible: Always Steps to Reproduce: 1. Pause the MCP [1] 2. Upgrade the cluster 3. Actual results: machine-config degraded [2]. Expected results: A message should be shown when trying to upgrade the cluster, and the upgrade should not start while the MCP are paused. Additional info: Could be use cases where the upgrade should be executed even if MCP paused. Maybe an option to not check the paused MCP could be added for those cases. [1] https://access.redhat.com/solutions/5477811 [2] https://access.redhat.com/solutions/5317441
> If MCP are paused while upgrading the cluster, the upgrade is not finishing and the machine-config cluster operator becomes degraded. Do you have a must-gather for this? Generally speaking, we expect to allow upgrades if the worker MCP is paused. This is the mechanism we plan to use to skip versions when upgrading. Or are you talking about masters?