Skip to content

OSDOCS#19052: Add z-stream release notes 4.20.18#109901

Merged
dfitzmau merged 1 commit intoopenshift:enterprise-4.20from
aksjoshi89:z-stream-4.20.18
Apr 14, 2026
Merged

OSDOCS#19052: Add z-stream release notes 4.20.18#109901
dfitzmau merged 1 commit intoopenshift:enterprise-4.20from
aksjoshi89:z-stream-4.20.18

Conversation

@aksjoshi89
Copy link
Copy Markdown
Contributor

@aksjoshi89 aksjoshi89 commented Apr 9, 2026

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 9, 2026
@ocpdocs-previewbot
Copy link
Copy Markdown

ocpdocs-previewbot commented Apr 9, 2026

🤖 Tue Apr 14 14:33:31 - Prow CI generated the docs preview:

https://109901--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-20-release-notes.html


* Before this release, global navigation satellite system (GNSS) serial port auto-detection issue in the grandmaster file caused GNSS port index changes after reboot, leading to node time synchronization issues. To work around this problem, remove `ts2phc.nmea_serialport` from the grandmaster `PTPConfig` and reboot the node. As a result, the GNSS port index number is no longer change after reboot, preventing time synchronization issues. (link:https://redhat.atlassian.net/browse/OCPBUGS-77749[OCPBUGS-77749])

* Before this update, insufficient /var/`ostree-container` partition size triggered image pull failure. As a consequence, end user deployment on Power using UPI and network boot failed due to insufficient partition size. With this release, the size of /var/`ostree-container` mount is increased to 5GB. As a result, image pull issues are resolved, improving deployment. (link:https://redhat.atlassian.net/browse/OCPBUGS-77896[OCPBUGS-77896])
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] RedHat.TermsErrors: Use 'user' rather than 'end user'. For more information, see RedHat.TermsErrors.


* Before this release, global navigation satellite system (GNSS) serial port auto-detection issue in the grandmaster file caused GNSS port index changes after reboot, leading to node time synchronization issues. To work around this problem, remove `ts2phc.nmea_serialport` from the grandmaster `PTPConfig` and reboot the node. As a result, the GNSS port index number is no longer change after reboot, preventing time synchronization issues. (link:https://redhat.atlassian.net/browse/OCPBUGS-77749[OCPBUGS-77749])

* Before this update, insufficient /var/`ostree-container` partition size triggered image pull failure. As a consequence, end user deployment on Power using UPI and network boot failed due to insufficient partition size. With this release, the size of /var/`ostree-container` mount is increased to 5GB. As a result, image pull issues are resolved, improving deployment. (link:https://redhat.atlassian.net/browse/OCPBUGS-77896[OCPBUGS-77896])
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] RedHat.TermsErrors: Use 'user-provisioned infrastructure' rather than 'UPI'. For more information, see RedHat.TermsErrors.


* Before this update, the slow refresh interval of OVN `EgressFirewall` Domain Name System (DNS) resolution caused a synchronization gap between the application's DNS resolution and the firewall controller's update cycle. As a consequence, slow DNS resolution in OVN egress firewall caused delay for application access after Network Load Balancer (NLB) recreation. With this release, the `EgressFirewall` DNS refresh interval has been adjusted for faster resolution. As a result, the `EgressFirewall` DNS resolution delay is reduced, improving the application's responsiveness. (link:https://redhat.atlassian.net/browse/OCPBUGS-79537[OCPBUGS-79537])

* Before this update, a nil pointer dereference occurred in the `sortUnpackJobs` function when sorting non-failed jobs. As a consequence, the catalog-operator Pod crashed during {sno} cluster installation, causing Operator installation failure. With this release, the nil pointer dereference is fixed, improving stability. As a result, the `catalog-operator` does not crash during {sno} cluster installation, ensuring smooth Operator installation. (link:https://redhat.atlassian.net/browse/OCPBUGS-79681[OCPBUGS-79681])
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.


* Before this update, a nil pointer dereference occurred in the `sortUnpackJobs` function when sorting non-failed jobs. As a consequence, the catalog-operator Pod crashed during {sno} cluster installation, causing Operator installation failure. With this release, the nil pointer dereference is fixed, improving stability. As a result, the `catalog-operator` does not crash during {sno} cluster installation, ensuring smooth Operator installation. (link:https://redhat.atlassian.net/browse/OCPBUGS-79681[OCPBUGS-79681])

* Before this update, the old {IBM Cloud} `vpc-go-sdk` version was unable to process `SecurityGroup` Rules with 'any' protocol, causing machine creation failures due to incompatibility with new Virtual Private Cloud (VPC) Security Group Rule. With this release, the VPC go Software Development Kit (SDK) has been updated to resolve the Security Group rule issue, allowing new `MachineSet` creation. As a result, the updated VPC Go SDK resolves the Security Group rule creation issue, enabling a new `MachineSet` to be provisioned without errors. (link:https://redhat.atlassian.net/browse/OCPBUGS-81317[OCPBUGS-81317])
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{ibm-cloud-title}' rather than the plain text product term 'IBM Cloud', unless your use case is an exception.

[id="zstream-4-20-18-updating_{context}"]
== Updating

To update an {product-title} 4.20 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 10, 2026
@aksjoshi89 aksjoshi89 changed the title OSDOCS#xx: Add z-stream release notes 4.20.18 OSDOCS#19052: Add z-stream release notes 4.20.18 Apr 10, 2026
@dfitzmau dfitzmau added branch/enterprise-4.20 and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Apr 10, 2026
Copy link
Copy Markdown
Contributor

@dfitzmau dfitzmau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, @aksjoshi89 . Nice work. I added comments, where some might need bug reporter input or a scan of the bug text.


* Before this release, global navigation satellite system (GNSS) serial port auto-detection issue in the grandmaster file caused GNSS port index changes after reboot, leading to node time synchronization issues. To work around this problem, remove `ts2phc.nmea_serialport` from the grandmaster `PTPConfig` and reboot the node. As a result, the GNSS port index number is no longer change after reboot, preventing time synchronization issues. (link:https://redhat.atlassian.net/browse/OCPBUGS-77749[OCPBUGS-77749])

* Before this update, insufficient /var/`ostree-container` partition size triggered image pull failure. As a consequence, end user deployment on Power using UPI and network boot failed due to insufficient partition size. With this release, the size of /var/`ostree-container` mount is increased to 5GB. As a result, image pull issues are resolved, improving deployment. (link:https://redhat.atlassian.net/browse/OCPBUGS-77896[OCPBUGS-77896])
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Before this update, insufficient /var/`ostree-container` partition size triggered image pull failure. As a consequence, end user deployment on Power using UPI and network boot failed due to insufficient partition size. With this release, the size of /var/`ostree-container` mount is increased to 5GB. As a result, image pull issues are resolved, improving deployment. (link:https://redhat.atlassian.net/browse/OCPBUGS-77896[OCPBUGS-77896])
* Before this update, insufficient `/var/ostree-container` partition size triggered image pull failure. As a consequence, an end-user deployment that runs on user-provisioned infrastructure for IBM Power and network boot failed due to insufficient partition size. With this release, the size of `/var/ostree-container` mount is increased to 5GB. As a result, image pull issues are resolved, improving deployment. (link:https://redhat.atlassian.net/browse/OCPBUGS-77896[OCPBUGS-77896])

This note is confusing. Power = IBM Power? If so (confirm with bug reporter), the attribute is {ibm-power-title}.

Why is the deployment running on "Power"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some parts of this are not fixed:

Screenshot From 2026-04-13 10-11-26

/var/ostree-container should be surrounded by backticks -> /var/ostree-container

@aksjoshi89
Copy link
Copy Markdown
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 14, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Apr 14, 2026

@aksjoshi89: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions 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.

@dfitzmau dfitzmau removed the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 14, 2026
@dfitzmau dfitzmau merged commit 4c2da86 into openshift:enterprise-4.20 Apr 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.20 size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants