OSDOCS#19052: Add z-stream release notes 4.20.18#109901
OSDOCS#19052: Add z-stream release notes 4.20.18#109901dfitzmau merged 1 commit intoopenshift:enterprise-4.20from
Conversation
|
🤖 Tue Apr 14 14:33:31 - Prow CI generated the docs preview: |
modules/zstream-4-20-18.adoc
Outdated
|
|
||
| * 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]) |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'user' rather than 'end user'. For more information, see RedHat.TermsErrors.
modules/zstream-4-20-18.adoc
Outdated
|
|
||
| * 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]) |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'user-provisioned infrastructure' rather than 'UPI'. For more information, see RedHat.TermsErrors.
modules/zstream-4-20-18.adoc
Outdated
|
|
||
| * 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]) |
There was a problem hiding this comment.
🤖 [error] Vale.Terms: Use 'Operators?' instead of 'operator'.
modules/zstream-4-20-18.adoc
Outdated
|
|
||
| * 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]) |
There was a problem hiding this comment.
🤖 [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]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
dfitzmau
left a comment
There was a problem hiding this comment.
Hi, @aksjoshi89 . Nice work. I added comments, where some might need bug reporter input or a scan of the bug text.
modules/zstream-4-20-18.adoc
Outdated
|
|
||
| * 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]) |
There was a problem hiding this comment.
| * 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"
30c72d8 to
456bb0a
Compare
|
/label merge-review-needed |
|
@aksjoshi89: 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. |

Version(s):
4.20
Issue:
OSDOCS-19052
Link to docs preview:
https://109901--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-20-release-notes.html#zstream-4-20-18_release-notes
QE review:
N/A
Additional information:
ART Dashboard Link:
https://art-dash.engineering.redhat.com/dashboard/release/openshift-4.20
Shipment Link:
https://gitlab.cee.redhat.com/hybrid-platforms/art/ocp-shipment-data/-/merge_requests/460/diffs#2b6b42520029cfef031e3f171793167d2c4e9531