Skip to content

OSDOCS-17044-3:[CQA] MACH-3: (UPI) Attachment4 - #116740

Open
tedaveryredhat wants to merge 1 commit into
openshift:mainfrom
tedaveryredhat:OSDOCS-17044-3
Open

OSDOCS-17044-3:[CQA] MACH-3: (UPI) Attachment4#116740
tedaveryredhat wants to merge 1 commit into
openshift:mainfrom
tedaveryredhat:OSDOCS-17044-3

Conversation

@tedaveryredhat

Copy link
Copy Markdown
Contributor

Version(s):
4.20+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-17044

Link to docs preview:

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 28, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 28, 2026

Copy link
Copy Markdown

@tedaveryredhat: This pull request references OSDOCS-17044 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.20+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-17044

Link to docs preview:

Additional information:

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 openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 28, 2026
@ocpdocs-previewbot

Copy link
Copy Markdown


[NOTE]
====
You can also xref:../../machine_management/creating_machinesets/creating-machineset-vsphere.adoc#creating-machineset-vsphere[use compute machine sets] to automate the creation of additional VMware vSphere compute machines for your cluster.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).


The following prerequisites must be met:

* You xref:../../installing/installing_vsphere/upi/installing-vsphere.adoc#installing-vsphere[installed a cluster on vSphere].

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).


* You xref:../../installing/installing_vsphere/upi/installing-vsphere.adoc#installing-vsphere[installed a cluster on vSphere].

* You have installation media and {op-system-first} images that you used to create your cluster. If you do not have these files, you must obtain them by following the instructions in the xref:../../installing/installing_vsphere/upi/installing-vsphere.adoc#installing-vsphere[installation procedure].

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).


[IMPORTANT]
====
If you do not have access to the {op-system-first} images that were used to create your cluster, you can add more compute machines to your {product-title} cluster with newer versions of {op-system-first} images. For instructions, see link:https://access.redhat.com/solutions/5514051[Adding new nodes to UPI cluster fails after upgrading to OpenShift 4.6+].

Copy link
Copy Markdown
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 'user-provisioned infrastructure' rather than 'UPI'. For more information, see RedHat.TermsErrors.

@openshift-ci

openshift-ci Bot commented Jul 28, 2026

Copy link
Copy Markdown

@tedaveryredhat: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/validate-portal 562a221 link true /test validate-portal

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants