-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS#6709: Misleading information in Driver Toolkit doc in 4.11 #55666
Conversation
@tshwartz: This pull request references Jira Issue OCPBUGS-6709, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 kubernetes/test-infra repository. |
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/10664 |
ad0551c
to
41ce2e2
Compare
41ce2e2
to
3d64e3f
Compare
@tshwartz: This pull request references Jira Issue OCPBUGS-6709, which is invalid:
Comment 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 kubernetes/test-infra repository. |
233915c
to
f1127f2
Compare
@tshwartz: No Jira issue is referenced in the title of this pull request. 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 kubernetes/test-infra repository. |
eb82550
to
fdf3eb2
Compare
c05dd00
to
d5826f4
Compare
/lgtm |
/lgtm |
/label telco |
/label peer-review-in-progress |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had a couple of comments/questions; otherwise, LGTM!
---- | ||
+ | ||
[IMPORTANT] | ||
==== | ||
ARM images are built for 64-bit Arm (AArch64) only, and are currently a Technology Preview feature. For more information about {product-title} on ARM, see xref:../release_notes/ocp-4-11-release-notes.html#ocp-4-11-release-notes[Release Notes]. For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ARM images are built for 64-bit Arm (AArch64) only, and are currently a Technology Preview feature. For more information about {product-title} on ARM, see xref:../release_notes/ocp-4-11-release-notes.html#ocp-4-11-release-notes[Release Notes]. For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope]. | |
ARM images are built for 64-bit ARM (AArch64) only, and are currently a Technology Preview feature. For more information about {product-title} on ARM, see xref:../release_notes/ocp-4-11-release-notes.html#ocp-4-11-release-notes[Release Notes]. For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe there is an exception for Telco docs (?) but usually xrefs aren't allowed in OCP modules (Release Notes link).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @kcarmichael08 Thanks for your feedback. I see other links in the section so I'll ping you later to finalize this.
@@ -28,17 +28,29 @@ The driver-toolkit image for the latest minor release will be tagged with the mi | |||
+ | |||
[source,terminal] | |||
---- | |||
$ oc adm release info 4.11.0 --image-for=driver-toolkit | |||
# For x86 image: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you need an explicit instruction to "run" or "enter" the command, and only one command per code block is allowed per https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/doc_guidelines.adoc#code-blocks-command-syntax-and-example-output
Maybe something like:
The image URL of the driver-toolkit
corresponding to a certain release can be extracted from the release image using the oc adm
command.
For an x86 image, enter the following command:
[example]
For an ARM image, enter the following command:
[example]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I copied this directly from the latest version published: https://docs.openshift.com/container-platform/4.12/hardware_enablement/psap-driver-toolkit.html Let's discuss this comment too.
/remove-label peer-review-in-progress |
New changes are detected. LGTM label has been removed. |
d74fec9
to
6d1dc60
Compare
/label merge-review-needed |
Title:
Misleading information in Driver Toolkit doc in 4.11
Summary of changes:
Updates to step 1 of the 'Finding the Driver Toolkit image URL in the payload' section.
Versions:
Enterprise 4.11
Issue:
(https://issues.redhat.com/browse/OCPBUGS-6709?filter=-1)
Link to docs preview:
http://file.emea.redhat.com/tshwartz/OCPBUGS-6709/hardware_enablement/psap-driver-toolkit.html
QE review:
Additional information: