OSDOCS-9535: RN update for microarchitecture requirement change #75457
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@obrown1205: This pull request references OSDOCS-9535 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
size/XS
|
🤖 Fri May 17 14:51:42 - Prow CI generated the docs preview: |
|
@obrown1205: This pull request references OSDOCS-9535 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/lgtm |
|
/cc |
|
As bug OSDOCS-9535 said, if we do not set cpu architecture will cause upgrade fail, so shall we highlight the statement here? |
I will add that note to the actual upgrade documentation for 4.13+. This PR just covers the release note update :) |
|
/lgtm |
|
Thank you @obrown1205 for the updates |
|
@obrown1205: This pull request references OSDOCS-9535 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/label peer-review-needed |
openshift-ci
bot
added
the
peer-review-needed
|
/remove-label peer-review-needed |
openshift-ci
bot
added
peer-review-in-progress
|
/remove-label peer-review-in-progress |
openshift-ci
bot
removed
the
peer-review-in-progress
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
skopacz1
added
merge-review-in-progress
|
Does this PR need change management? Seems like it might but I just wanted to check |
skopacz1
removed
merge-review-in-progress
|
/lgtm |
|
@obrown1205: This pull request references OSDOCS-9535 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
|
/label merge-review-in-progress |
|
/remove-label merge-review-needed |
openshift-ci
bot
added
merge-review-in-progress
|
|
||
| {product-title} {product-version} is based on {op-system-base-full} 9.2. {op-system-base} 9.2 has not yet been submitted for FIPS validation. Red Hat expects, though cannot commit to a specific timeframe, to obtain FIPS validation for {op-system-base} 9.0 and {op-system-base} 9.2 modules, and later even minor releases of {op-system-base} 9.x. Updates will be available in link:https://access.redhat.com/articles/2918071[Compliance Activities and Government Standards]. | ||
|
|
||
| Because {product-title} 4.13 is based on the RHEL 9.2 host operating system, the micro-architecture requirements are now increased to x86-64-v2, Power9, and Z14. See the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.0_release_notes/index#architectures[RHEL micro-architecture requirements documentation]. You can verify compatibility before updating by following the procedures outlined in this link:https://access.redhat.com/solutions/7052996[KCS article]. |
There was a problem hiding this comment.
| Because {product-title} 4.13 is based on the RHEL 9.2 host operating system, the micro-architecture requirements are now increased to x86-64-v2, Power9, and Z14. See the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.0_release_notes/index#architectures[RHEL micro-architecture requirements documentation]. You can verify compatibility before updating by following the procedures outlined in this link:https://access.redhat.com/solutions/7052996[KCS article]. | |
| Because {product-title} 4.13 is based on the {op-system-base} 9.2 host operating system, the micro-architecture requirements are now increased to x86_64-v2, Power9, and Z14. See the link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/9.0_release_notes/index#architectures[RHEL micro-architecture requirements documentation]. You can verify compatibility before updating by following the procedures outlined in this link:https://access.redhat.com/solutions/7052996[KCS article]. |
https://redhat-documentation.github.io/supplementary-style-guide/#x86_64 for the arches
There was a problem hiding this comment.
Since this is an addition to the main body of the release notes, does this need change management?
There was a problem hiding this comment.
Nope! I added to the additional notes section of the PR - I checked with @kalexand-rh , @sferich888 , @sjstout and @sdodson and they all agreed that we do not need change management here.
|
/remove-label merge-review-in-progress |
openshift-ci
bot
removed
the
merge-review-in-progress
|
New changes are detected. LGTM label has been removed. |
|
@obrown1205: all tests passed! Full PR test history. Your PR dashboard. 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. |
10 participants
Version(s):
4.13
Issue:
https://issues.redhat.com/browse/OSDOCS-9535
Link to docs preview:
https://75457--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-13-release-notes.html
QE review:
Additional information:
No change management required - confirmed