Skip to content

OSDOCS-17045-2: CQA 1 for MACH-4 Cluster API for Compute Machines#114216

Open
dfitzmau wants to merge 1 commit into
openshift:mainfrom
dfitzmau:OSDOCS-17045-2
Open

OSDOCS-17045-2: CQA 1 for MACH-4 Cluster API for Compute Machines#114216
dfitzmau wants to merge 1 commit into
openshift:mainfrom
dfitzmau:OSDOCS-17045-2

Conversation

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

openshift-ci-robot commented Jun 26, 2026

Copy link
Copy Markdown

@dfitzmau: This pull request references OSDOCS-17045 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:
OSDOCS-17045

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.

@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 26, 2026
@dfitzmau dfitzmau force-pushed the OSDOCS-17045-2 branch 2 times, most recently from 786bccc to 8653139 Compare June 26, 2026 13:39
@openshift-ci 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 26, 2026
@dfitzmau dfitzmau force-pushed the OSDOCS-17045-2 branch 6 times, most recently from 9a22627 to e817768 Compare June 26, 2026 14:30
`kind`:: Specifies the resource kind of the resource that you want to migrate. For example, the resource kind for a compute machine set is `MachineSet` and the resource kind for a compute machine is `Machine`.
`metadata.name`:: Specifies the name of the resource that you want to migrate.
`spec.authoritativeAPI`:: Specifies the authoritative API that you want this resource to use. For example, to start migrating a {from-api-name} resource to the {to-api-name}, specify `{to-api-value}`.
`status.authoritativeAPI`:: Specifies the value for the current authoritative API. This value indicates which API currently manages this resource. Do not change the value in this part of the specification.

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.Spacing: Keep one space between words in 'resource. Do'. For more information, see RedHat.Spacing.

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

openshift-ci-robot commented Jun 26, 2026

Copy link
Copy Markdown

@dfitzmau: This pull request references OSDOCS-17045 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:
OSDOCS-17045

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.

@openshift-ci

openshift-ci Bot commented Jun 26, 2026

Copy link
Copy Markdown

@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 dfitzmau added the merge-review-needed Signifies that the merge review team needs to review this PR label Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 branch/enterprise-5.0 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. merge-review-needed Signifies that the merge review team needs to review this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants