OSDOCS#19970: Add installer RNs for 4.22 (bug batching)#112608
Merged
Conversation
openshift-ci
Bot
added
the
size/S
|
🤖 Tue Jun 02 14:28:25 - Prow CI generated the docs preview: |
tmalove
force-pushed
the
OSDOCS-19970
branch
3 times, most recently
from
a388140 to
2aa6bd0
Compare
Contributor
Author
|
/label merge-review-needed |
openshift-ci
Bot
added
the
merge-review-needed
dfitzmau
added
branch/enterprise-4.22
merge-review-in-progress
dfitzmau
reviewed
Jun 2, 2026
|
|
||
| * Before this update, installing a cluster on {gcp-first} in the `us-south1` or `us-central1` regions without specifying zones in the `install-config.yaml` file caused the installation failures. As a consequence, the installation program automatically selected an AI zone by default and because these specialized zones often lacked the specific machine types required for control plane and compute nodes, the installation failed. With this release, these AI zones are excluded from the installation program default zone selection logic. As a result, the installation program selects compatible zones by default. (link: https://redhat.atlassian.net/browse/OCPBUGS-74625[OCPBUGS-74625]) | ||
|
|
||
| * Before this update, attempting to use custom DNS on {azure-short} Stack Hub, which is not supported, caused the custom DNS installation to fail. With this release, the installation program validates {azure-short} Stack Hub for custom DNS support, preventing unsupported installations. As a result, the installation program exits with an error message for an unsupported custom DNS on {azure-short} Stack Hub. (link: https://redhat.atlassian.net/browse/OCPBUGS-74631[OCPBUGS-74631]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * Before this update, attempting to use custom DNS on {azure-short} Stack Hub, which is not supported, caused the custom DNS installation to fail. With this release, the installation program validates {azure-short} Stack Hub for custom DNS support, preventing unsupported installations. As a result, the installation program exits with an error message for an unsupported custom DNS on {azure-short} Stack Hub. (link: https://redhat.atlassian.net/browse/OCPBUGS-74631[OCPBUGS-74631]) | |
| * Before this update, attempting to use custom DNS on {azure-short} Stack Hub, which is not supported, caused the custom DNS installation to fail. With this release, the installation program validates {azure-short} Stack Hub for custom DNS support, preventing unsupported installations. As a result, the installation program exits with an error message for an unsupported custom DNS on {azure-short} Stack Hub. (link:https://redhat.atlassian.net/browse/OCPBUGS-74631[OCPBUGS-74631]) |
|
|
||
| * Before this update, attempting to install a cluster on {azure-first} using reserved keywords or trademarks caused the installation program to fail. Cluster names containing words such as `microsoft`, `windows`, `login`, `azure`, `office` caused errors during resource provisioning, and errors related to the resource or domain name were reported. As a consequence, users had to manually troubleshoot and identify the prohibited words while installing the cluster. With this release, the installation program validates the cluster name against 43 {azure-short} reserved words before deploying the cluster and provides clear error messages if a prohibited word is detected. As a result, installation failures are prevented before any cloud resources are created. (link:https://redhat.atlassian.net/browse/OCPBUGS-66943[OCPBUGS-66943]) | ||
|
|
||
| * Before this update, if the {op-system-first} image was not explicitly specified, the installation program could not generate {azure-first} machine sets for the Hive Operator. As a consequence of the change to global marketplace images, machine sets generated by the installation program became invalid, causing Hive Operator machine pool scaling operations to fail. With this release, the installation program handles calls without an {op-system} image by using the machine API Operator default image selection and ensuring the correct machine sets for the Hive Operator. (link:https://redhat.atlassian.net/browse/OCPBUGS-67310[OCPBUGS-67310]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * Before this update, if the {op-system-first} image was not explicitly specified, the installation program could not generate {azure-first} machine sets for the Hive Operator. As a consequence of the change to global marketplace images, machine sets generated by the installation program became invalid, causing Hive Operator machine pool scaling operations to fail. With this release, the installation program handles calls without an {op-system} image by using the machine API Operator default image selection and ensuring the correct machine sets for the Hive Operator. (link:https://redhat.atlassian.net/browse/OCPBUGS-67310[OCPBUGS-67310]) | |
| * Before this update, if the {op-system-first} image was not explicitly specified, the installation program could not generate {azure-first} machine sets for the Hive Operator. As a consequence of the change to global marketplace images, machine sets generated by the installation program became invalid, causing Hive Operator machine pool scaling operations to fail. With this release, the installation program handles calls without an {op-system} image by using the machine API Operator default image selection and ensures the correct machine sets for the Hive Operator. (link:https://redhat.atlassian.net/browse/OCPBUGS-67310[OCPBUGS-67310]) |
|
|
||
| * Before this update, insufficient disk space for a large node image download prevented {product-title} 4.20.8 deployment. As a consequence, users failed to install {product-title} 4.20.8. With this release, temporary storage space for {product-title} 4.20.8 installation is increased. As a result, users can deploy {product-title} 4.20.8 with large image support. (link:https://redhat.atlassian.net/browse/OCPBUGS-70168[OCPBUGS-70168]) | ||
|
|
||
| * Before this update, installing a cluster on {gcp-first} in the `us-south1` or `us-central1` regions without specifying zones in the `install-config.yaml` file caused the installation failures. As a consequence, the installation program automatically selected an AI zone by default and because these specialized zones often lacked the specific machine types required for control plane and compute nodes, the installation failed. With this release, these AI zones are excluded from the installation program default zone selection logic. As a result, the installation program selects compatible zones by default. (link: https://redhat.atlassian.net/browse/OCPBUGS-74625[OCPBUGS-74625]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * Before this update, installing a cluster on {gcp-first} in the `us-south1` or `us-central1` regions without specifying zones in the `install-config.yaml` file caused the installation failures. As a consequence, the installation program automatically selected an AI zone by default and because these specialized zones often lacked the specific machine types required for control plane and compute nodes, the installation failed. With this release, these AI zones are excluded from the installation program default zone selection logic. As a result, the installation program selects compatible zones by default. (link: https://redhat.atlassian.net/browse/OCPBUGS-74625[OCPBUGS-74625]) | |
| * Before this update, installing a cluster on {gcp-first} in the `us-south1` or `us-central1` regions without specifying zones in the `install-config.yaml` file caused installation failures. As a consequence, the installation program automatically selected an AI zone by default and because these specialized zones often lacked the specific machine types required for control plane and compute nodes, the installation failed. With this release, these AI zones are excluded from the installation program default zone selection logic. As a result, the installation program selects compatible zones by default. (link:https://redhat.atlassian.net/browse/OCPBUGS-74625[OCPBUGS-74625]) |
|
|
||
| * Before this update, the {sno} cluster's Machine Config Operator (MCO) lease acquisition was delayed due to inflated leader election timings during node reboots. Consequently, the MCO controller took longer to acquire the lease, causing delayed configuration updates. With this release, the MCO lease acquisition time after reboots on {sno} clusters is reduced. As a result, MCO lease acquisition time is improved, enhancing cluster stability in {sno} clusters. (link: https://redhat.atlassian.net/browse/OCPBUGS-78154[OCPBUGS-78154]) | ||
|
|
||
| * With this update, the {ibm-power-server-title} {cluster-capi-operator} is enhanced to `v0.12.2` in {product-title} version 4.22. Users are required to manually select the appropriate partner group in the `Contributing Group` field due to multiple partner confidential group memberships. This feature ensures compatibility, improves system performance, and maintains security by proper selection of partner groups. The result is an {product-title} deployment with improved overall performance and reliability. (link: https://redhat.atlassian.net/browse/OCPBUGS-83611[OCPBUGS-83611]) |
Contributor
There was a problem hiding this comment.
Move OCPBUGS-83611 to an enhancement section?
Contributor
Author
There was a problem hiding this comment.
Moved to New features and enhancements section.
|
|
||
| * Before this update, attempting to use custom DNS on {azure-short} Stack Hub, which is not supported, caused the custom DNS installation to fail. With this release, the installation program validates {azure-short} Stack Hub for custom DNS support, preventing unsupported installations. As a result, the installation program exits with an error message for an unsupported custom DNS on {azure-short} Stack Hub. (link: https://redhat.atlassian.net/browse/OCPBUGS-74631[OCPBUGS-74631]) | ||
|
|
||
| * Before this update, the {sno} cluster's Machine Config Operator (MCO) lease acquisition was delayed due to inflated leader election timings during node reboots. Consequently, the MCO controller took longer to acquire the lease, causing delayed configuration updates. With this release, the MCO lease acquisition time after reboots on {sno} clusters is reduced. As a result, MCO lease acquisition time is improved, enhancing cluster stability in {sno} clusters. (link: https://redhat.atlassian.net/browse/OCPBUGS-78154[OCPBUGS-78154]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * Before this update, the {sno} cluster's Machine Config Operator (MCO) lease acquisition was delayed due to inflated leader election timings during node reboots. Consequently, the MCO controller took longer to acquire the lease, causing delayed configuration updates. With this release, the MCO lease acquisition time after reboots on {sno} clusters is reduced. As a result, MCO lease acquisition time is improved, enhancing cluster stability in {sno} clusters. (link: https://redhat.atlassian.net/browse/OCPBUGS-78154[OCPBUGS-78154]) | |
| * Before this update, the {sno} cluster's Machine Config Operator (MCO) lease acquisition was delayed due to inflated leader election timings during node reboots. As a consequence, the MCO controller took longer to acquire the lease, causing delayed configuration updates. With this release, the MCO lease acquisition time after reboots on {sno} clusters is reduced. As a result, MCO lease acquisition time is improved, enhancing cluster stability in {sno} clusters. (link: https://redhat.atlassian.net/browse/OCPBUGS-78154[OCPBUGS-78154]) |
dfitzmau
removed
the
merge-review-in-progress
|
@tmalove: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version(s):
4.22
Issue:
OSDOCS-19970
Link to docs preview:
Installer
Installation and update
QE review:
N/A for RNs