Skip to content

Conversation

@jhradilek
Copy link
Contributor

Version(s): 4.20

Issue: CNV-62649

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
This is a manual cherry-pick for PR #102522 as the openshift-cherrypick-robot failed with the following error:

status code 406 not one of [200], body:
 {
  "message":"Sorry, the diff exceeded the maximum number of files (300). Consider using 'List pull requests files' API or locally cloning the repository instead.",
  "errors": [
    {
      "resource":"PullRequest",
      "field":"diff",
      "code":"too_large"
    }
  ],
  "documentation_url":"https://docs.github.com/rest/pulls/pulls#list-pull-requests-files",
  "status":"406"
}

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 18, 2025

@jhradilek: This pull request references CNV-62649 which is a valid jira issue.

In response to this:

Version(s): 4.20

Issue: CNV-62649

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
This is a manual cherry-pick for PR #102522 as the openshift-cherrypick-robot failed with the following error:

status code 406 not one of [200], body:
{
 "message":"Sorry, the diff exceeded the maximum number of files (300). Consider using 'List pull requests files' API or locally cloning the repository instead.",
 "errors": [
   {
     "resource":"PullRequest",
     "field":"diff",
     "code":"too_large"
   }
 ],
 "documentation_url":"https://docs.github.com/rest/pulls/pulls#list-pull-requests-files",
 "status":"406"
}

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.

@jhradilek
Copy link
Contributor Author

/label cnv

@jhradilek jhradilek requested a review from ousleyp November 18, 2025 15:42
@openshift-ci openshift-ci bot added CNV Label for all CNV PRs size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Nov 18, 2025
@jhradilek jhradilek changed the title [enterprise-4.21] CNV-62649: Updated CNV modules to pass DITA validation [enterprise-4.20] CNV-62649: Updated CNV modules to pass DITA validation Nov 18, 2025
@ocpdocs-previewbot
Copy link

🤖 Tue Nov 18 15:55:52 - Prow CI generated the docs preview:
https://102691--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt


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.
Copy link
Collaborator

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.
Copy link
Collaborator

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.
Copy link
Collaborator

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.
Copy link
Collaborator

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.
Copy link
Collaborator

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.
Copy link
Collaborator

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.

@openshift-ci
Copy link

openshift-ci bot commented Nov 18, 2025

@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.

@ousleyp
Copy link
Member

ousleyp commented Nov 18, 2025

LGTM

@jhradilek jhradilek merged commit a8a4179 into openshift:enterprise-4.20 Nov 18, 2025
2 checks passed
@jhradilek jhradilek deleted the cnv-modules-dita-prep-4.20 branch November 18, 2025 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CNV Label for all CNV PRs jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants