OSDOCS-16988-4-CQA-1:CQA PR 4.1 for INSTALL-1: Core Installation Conc… by dfitzmau · Pull Request #113598 · openshift/openshift-docs

dfitzmau · 2026-06-18T08:44:55Z

Version(s):
4.20+

Link to docs preview:

openshift-ci-robot · 2026-06-18T08:44:57Z

@dfitzmau: No Jira issue with key CQA-1 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Version(s):
4.20+

Issue:
OSDOCS-16988

Link to docs preview:

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.

ocpdocs-previewbot · 2026-06-18T09:00:24Z

🤖 Thu Jun 18 14:57:32 - Prow CI generated the docs preview:

https://113598--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/validation_and_troubleshooting/validating-an-installation.html
https://113598--ocpdocs-pr.netlify.app/openshift-enterprise/latest/post_installation_configuration/changing-cloud-credentials-configuration.html

openshift-ci-robot · 2026-06-18T10:31:25Z

@dfitzmau: No Jira issue with key CQA-1 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

Version(s):
4.20+

Issue:
OSDOCS-16988

Link to docs preview:

https://113598--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/validation_and_troubleshooting/validating-an-installation.html

https://113598--ocpdocs-pr.netlify.app/openshift-enterprise/latest/post_installation_configuration/changing-cloud-credentials-configuration.html

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.

mburke5678 · 2026-06-18T13:14:30Z

 toc::[]

+[role="_abstract"]
 You can check the status of an {product-title} cluster after an installation or validate boot artifacts before an installation by following the procedures in this document.


@dfitzmau

following the procedures in this document

Is this not self-referential?

Yes. Removed.

mburke5678 · 2026-06-18T13:15:04Z

 ----

-* Verify that the components are using short-term security credentials for individual components by running the following command:
+* Verify that the components are using short-term security credentials by running the following command:


Why make this change?

mburke5678 · 2026-06-18T13:19:10Z

 * The cluster's resource usage

-. Optional: You can view information about your cluster that {red-hat-lightspeed} collects by navigating to the *Overview* menu. From this menu you can view the following information:
+. Optional: Navigate to the *Overview* menu to view information that {red-hat-lightspeed} collects about your cluster:


You changed Navigate to Go in a previous step. Should you make the change here also for consistency?

mburke5678 · 2026-06-18T13:20:54Z


-You can review the following information in the *Overview* page in the {product-title} web console:
+[role="_abstract"]
+You can specific information in the *Overview* page in the {product-title} web console.


Missing a verb here.

Suggested change

You can specific information in the *Overview* page in the {product-title} web console.

You can view specific information in the *Overview* page in the {product-title} web console.

Suggested change

You can specific information in the *Overview* page in the {product-title} web console.

You can review specific information in the *Overview* page in the {product-title} web console.

mburke5678 · 2026-06-18T13:21:26Z

+[role="_abstract"]
+You can specific information in the *Overview* page in the {product-title} web console.
+
+The *Overview* page can display the following information:


Can display? Why would it not?

mburke5678 · 2026-06-18T13:24:08Z


-You can review a summary of an installation in the {product-title} installation log. If an installation succeeds, the information required to access the cluster is included in the log.
+[role="_abstract"]
+The {product-title} installation log contains a summary of the installation. If installation succeeds, the log includes the information required to access the cluster.


I know this is existing text, but If installation succeeds seems weak to me. Of course the install will succeed!! Maybe:

Suggested change

The {product-title} installation log contains a summary of the installation. If installation succeeds, the log includes the information required to access the cluster.

The {product-title} installation log contains a summary of the installation, including the information required to access the cluster after installation.

mburke5678 · 2026-06-18T13:26:18Z

+[role="_abstract"]
 The {product-title} installation program contains pinned versions of {op-system} bootimages. Fully automated installations use these pinned artifacts by default. The mirror registry where you downloaded the installation program contains a `sha256sum` encrypted with the Red{nbsp}Hat product key.

 For user-provisioned infrastructure installations, you can access information and use the {product-title} installer to indirectly validate {op-system} bootimage artifacts using their SHA-256 checksums.


This sounds like a better short desc to me. This is what the module is about, yah?

you can access information and use the {product-title} installer to indirectly validate {op-system} bootimage artifacts using their SHA-256 checksums.

mburke5678 · 2026-06-18T13:33:18Z

@dfitzmau A few comments for your consideration.

openshift-ci · 2026-06-18T14:58:56Z

@dfitzmau: 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 · 2026-06-18T14:59:55Z

/cherrypick enterprise-4.22

dfitzmau · 2026-06-18T14:59:59Z

/cherrypick enterprise-4.21

dfitzmau · 2026-06-18T15:00:03Z

/cherrypick enterprise-4.20

dfitzmau · 2026-06-18T15:00:11Z

/cherrypick enterprise-5.0

openshift-cherrypick-robot · 2026-06-18T15:00:53Z

@dfitzmau: new pull request created: #113635

Details

In response to this:

/cherrypick enterprise-4.22

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.

openshift-cherrypick-robot · 2026-06-18T15:00:55Z

@dfitzmau: #113598 failed to apply on top of branch "enterprise-4.21":

Applying: OSDOCS-16988-4-CQA-1:CQA PR 4.1 for INSTALL-1: Core Installation Conc…
Using index info to reconstruct a base tree...
M	installing/validation_and_troubleshooting/validating-an-installation.adoc
M	modules/querying-the-status-of-cluster-nodes-using-the-cli.adoc
Falling back to patching base and 3-way merge...
Auto-merging installing/validation_and_troubleshooting/validating-an-installation.adoc
CONFLICT (content): Merge conflict in installing/validation_and_troubleshooting/validating-an-installation.adoc
Auto-merging modules/querying-the-status-of-cluster-nodes-using-the-cli.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 OSDOCS-16988-4-CQA-1:CQA PR 4.1 for INSTALL-1: Core Installation Conc…

Details

In response to this:

/cherrypick enterprise-4.21

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.

openshift-cherrypick-robot · 2026-06-18T15:01:05Z

@dfitzmau: #113598 failed to apply on top of branch "enterprise-4.20":

Patch is empty.
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To record the empty patch as an empty commit, run "git am --allow-empty".
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

Details

In response to this:

/cherrypick enterprise-4.20

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.

openshift-cherrypick-robot · 2026-06-18T15:01:15Z

@dfitzmau: new pull request created: #113636

Details

In response to this:

/cherrypick enterprise-5.0

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.

openshift-ci Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 18, 2026

dfitzmau force-pushed the OSDOCS-16988-4-CQA-1 branch from 8dd75f7 to c1ebfdc Compare June 18, 2026 09:14

openshift-ci Bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 18, 2026

dfitzmau added branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 branch/enterprise-5.0 labels Jun 18, 2026

dfitzmau force-pushed the OSDOCS-16988-4-CQA-1 branch 5 times, most recently from 77f1886 to a8b0821 Compare June 18, 2026 10:28

dfitzmau force-pushed the OSDOCS-16988-4-CQA-1 branch from a8b0821 to e878cb8 Compare June 18, 2026 10:41

dfitzmau added the merge-review-needed Signifies that the merge review team needs to review this PR label Jun 18, 2026

mburke5678 reviewed Jun 18, 2026

View reviewed changes

Comment thread modules/rhcos-validate-live-media.adoc

mburke5678 added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Jun 18, 2026

OSDOCS-16988-4-CQA-1:CQA PR 4.1 for INSTALL-1: Core Installation Conc…

afbb979

dfitzmau force-pushed the OSDOCS-16988-4-CQA-1 branch from e878cb8 to afbb979 Compare June 18, 2026 14:32

openshift-ci Bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jun 18, 2026

dfitzmau merged commit 707e9f3 into openshift:main Jun 18, 2026
2 checks passed

openshift-cherrypick-robot mentioned this pull request Jun 18, 2026

[enterprise-4.22] OSDOCS-16988-4-CQA-1:CQA PR 4.1 for INSTALL-1: Core Installation Conc… #113635

Merged

openshift-cherrypick-robot mentioned this pull request Jun 18, 2026

[enterprise-5.0] OSDOCS-16988-4-CQA-1:CQA PR 4.1 for INSTALL-1: Core Installation Conc… #113636

Merged

This was referenced Jun 18, 2026

[enterprise-4.21] OSDOCS-16988-4-CQA-1:CQA PR 4.1 for INSTALL-1: Core Installation Conc… #113637

Merged

[enterprise-4.20] OSDOCS-16988-4-CQA-1:CQA PR 4.1 for INSTALL-1: Core Installation Conc… #113641

Merged

	You can specific information in the Overview page in the {product-title} web console.
	You can view specific information in the Overview page in the {product-title} web console.

	You can specific information in the Overview page in the {product-title} web console.
	You can review specific information in the Overview page in the {product-title} web console.

	The {product-title} installation log contains a summary of the installation. If installation succeeds, the log includes the information required to access the cluster.
	The {product-title} installation log contains a summary of the installation, including the information required to access the cluster after installation.

Conversation

dfitzmau commented Jun 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Jun 18, 2026

Uh oh!

ocpdocs-previewbot commented Jun 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Jun 18, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

mburke5678 commented Jun 18, 2026

Uh oh!

openshift-ci Bot commented Jun 18, 2026

Uh oh!

Uh oh!

dfitzmau commented Jun 18, 2026

Uh oh!

dfitzmau commented Jun 18, 2026

Uh oh!

dfitzmau commented Jun 18, 2026

Uh oh!

dfitzmau commented Jun 18, 2026

Uh oh!

openshift-cherrypick-robot commented Jun 18, 2026

Uh oh!

openshift-cherrypick-robot commented Jun 18, 2026

Uh oh!

openshift-cherrypick-robot commented Jun 18, 2026

Uh oh!

openshift-cherrypick-robot commented Jun 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

dfitzmau commented Jun 18, 2026 •

edited

Loading

ocpdocs-previewbot commented Jun 18, 2026 •

edited

Loading