Skip to content

OSDOCS-11940: specify Arm nodes not yet available for Virtualization #91369

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

Merged
merged 1 commit into from
Apr 2, 2025

Conversation

jneczypor
Copy link
Contributor

@jneczypor jneczypor commented Mar 31, 2025

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

openshift-ci-robot commented Mar 31, 2025

@jneczypor: This pull request references OSDOCS-11940 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

OSDOCS-11940: specify Arm nodes not yet available for Virtualization

Version(s):
4.18+

Issue:
https://issues.redhat.com/browse/OSDOCS-11940

Link to docs preview:

QE review:

  • QE has approved this change.

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/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 31, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 1, 2025

@jneczypor: This pull request references OSDOCS-11940 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

OSDOCS-11940: specify Arm nodes not yet available for Virtualization

Version(s):
4.18+

Issue:
https://issues.redhat.com/browse/OSDOCS-11940

Link to docs preview:
OCP: https://91369--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/about_virt/about-virt.html
ROSA Classic: https://91369--ocpdocs-pr.netlify.app/openshift-rosa/latest/virt/about_virt/about-virt.html
ROSA HCP: https://91369--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/virt/about_virt/about-virt.html

QE review:
No QE needed

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.

@jneczypor
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Apr 1, 2025
Copy link
Contributor

@arendej arendej left a comment

Choose a reason for hiding this comment

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

LGTM

@xenolinux xenolinux added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Apr 2, 2025
@xenolinux xenolinux added this to the Continuous Release milestone Apr 2, 2025
Copy link
Contributor

@xenolinux xenolinux left a comment

Choose a reason for hiding this comment

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

One comment; lgtm

@xenolinux xenolinux added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Apr 2, 2025
Copy link

openshift-ci bot commented Apr 2, 2025

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

@jneczypor
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 2, 2025
@EricPonvelle EricPonvelle added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Apr 2, 2025
Copy link
Contributor

@EricPonvelle EricPonvelle left a comment

Choose a reason for hiding this comment

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

/lgtm

@EricPonvelle EricPonvelle merged commit 4f2240a into openshift:main Apr 2, 2025
2 checks passed
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2025
@EricPonvelle EricPonvelle removed lgtm Indicates that a PR is ready to be merged. merge-review-in-progress Signifies that the merge review team is reviewing this PR labels Apr 2, 2025
@EricPonvelle
Copy link
Contributor

/cherrypick enterprise-4.18

@EricPonvelle
Copy link
Contributor

/cherrypick enterprise-4.19

@openshift-cherrypick-robot

@EricPonvelle: new pull request created: #91554

In response to this:

/cherrypick enterprise-4.18

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.

@openshift-cherrypick-robot

@EricPonvelle: new pull request created: #91555

In response to this:

/cherrypick enterprise-4.19

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.18 branch/enterprise-4.19 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants