ROSA upgrade issue mitigation for HOSTEDCP-1941
ROSA with Hosted Control Plane clusters and HyperShift clusters with following properties are affected by the This content is not included.issue :
ROSA with hosted control planes clusters with:
- A Control Plane version at or later than 4.15.23 but at or earlier than 4.15.30 or at or later than 4.16.4 and at or earlier than 4.16.10, and
- MachinePools with version 4.14.33 or earlier or 4.15.22 or earlier.
4.16.z MachinePools are not affected, regardless of Control Plane version.
For OpenShift clusters with the Hypershift Operator
- A Control Plane version at or later than 4.15.23 but at or earlier than 4.15.30 or at or later than 4.16.4 and at or earlier than 4.16.10, and
- Node Pools with version 4.14.33 or earlier or 4.15.22 or earlier.
4.16.z NodePools are not affected, regardless of Hosted cluster version.
For clusters with this condition node/machine pools will not be able to auto-scale or add additional nodes.
( Related article: 7085089 )
Further to the above issue identified August 30, 2024, Red Hat has temporarily blocked clusters from upgrading into these versions, so as to mitigate the impact to customer clusters.
In summary, the following upgrades are temporarily blocked for ROSA (both classic and HCP):
- 4.14.* to 4.15.23 through 4.15.30
- 4.15.0 through 4.15.22 to 4.15.23-4.15.30
- 4.15.0 through 4.15.22 to 4.16.0-4.16.10
If your cluster was impacted as notified on August 30, 2024, there are two options to work around this issue:
- (For ROSA w/ HCP) If your control plane is already on 4.15.23 or above, create a new machine pool of version 4.15.23 or newer
- Apply the fixed version via upgrade: 4.15.31 or later and 4.16.11 or later.
If you have further questions, please submit a support case.