-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[enterprise-4.20] CNV-62649: Updated CNV modules to pass DITA validation #102691
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
[enterprise-4.20] CNV-62649: Updated CNV modules to pass DITA validation #102691
Conversation
|
@jhradilek: This pull request references CNV-62649 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 cnv |
|
🤖 Tue Nov 18 15:55:52 - Prow CI generated the docs preview: |
|
|
||
| The Tekton Tasks Operator, `tekton-tasks-operator`, deploys example pipelines showing the usage of OpenShift Pipelines for virtual machines (VMs). This operator also deploys additional OpenShift Pipeline tasks that allow users to create VMs from templates, copy and modify templates, and create data volumes. | ||
| [role="_abstract"] | ||
| The Tekton Tasks Operator, `tekton-tasks-operator`, deploys example pipelines showing the usage of OpenShift Pipelines for virtual machines (VMs). It also deploys additional OpenShift Pipeline tasks that allow users to create VMs from templates, copy and modify templates, and create data volumes. |
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.
🤖 [error] OpenShiftAsciiDoc.SuggestAttribute: Use the AsciiDoc attribute '{pipelines-shortname}' rather than the plain text product term 'OpenShift Pipelines', unless your use case is an exception.
| The following error messages might appear in {VirtProductName} logs. | ||
|
|
||
| `ErrImagePull` or `ImagePullBackOff`:: Indicates an incorrect deployment configuration or problems with the images that are referenced. | ||
| `ErrImagePull` or `ImagePullBackOff`:: Indicates an incorrect deployment configuration or problems with the images that are referenced. |
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.
🤖 [error] Vale.Avoid: Avoid using 'deployment configuration'.
| The following error messages might appear in {VirtProductName} logs. | ||
|
|
||
| `ErrImagePull` or `ImagePullBackOff`:: Indicates an incorrect deployment configuration or problems with the images that are referenced. | ||
| `ErrImagePull` or `ImagePullBackOff`:: Indicates an incorrect deployment configuration or problems with the images that are referenced. |
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.
🤖 [error] RedHat.TermsErrors: Use 'deployment' rather than 'deployment configuration'. For more information, see RedHat.TermsErrors.
| ] | ||
| ---- | ||
| <1> The hot plugged interface appears in the VMI status. | ||
| <1> The hot plugged interface appears in the VMI status. |
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.
🤖 [error] AsciiDocDITA.CalloutList: Callouts are not supported in DITA.
| @@ -6,7 +6,10 @@ | |||
| [id="virt-maintaining-bare-metal-nodes_{context}"] | |||
| = Maintaining bare metal nodes | |||
|
|
|||
| When you deploy {product-title} on bare metal infrastructure, there are additional considerations that must be taken into account compared to deploying on cloud infrastructure. Unlike in cloud environments where the cluster nodes are considered ephemeral, re-provisioning a bare metal node requires significantly more time and effort for maintenance tasks. | |||
| [role="_abstract"] | |||
| When you deploy {product-title} on bare metal infrastructure, there are additional considerations that must be taken into account compared to deploying on cloud infrastructure. | |||
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.
🤖 [error] RedHat.TermsErrors: Use 'bare-metal infrastructure' rather than 'bare metal infrastructure'. For more information, see RedHat.TermsErrors.
| [role="_abstract"] | ||
| When you deploy {product-title} on bare metal infrastructure, there are additional considerations that must be taken into account compared to deploying on cloud infrastructure. | ||
|
|
||
| Unlike in cloud environments where the cluster nodes are considered ephemeral, re-provisioning a bare metal node requires significantly more time and effort for maintenance tasks. |
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.
🤖 [error] RedHat.TermsErrors: Use 'bare-metal node' rather than 'bare metal node'. For more information, see RedHat.TermsErrors.
|
@jhradilek: 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. |
|
LGTM |
Version(s): 4.20
Issue: CNV-62649
Link to docs preview:
QE review:
Additional information:
This is a manual cherry-pick for PR #102522 as the
openshift-cherrypick-robotfailed with the following error: