Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[release-4.18] OCPBUGS-48240: remove the types which failed by RHEL-59521 and add the new gpu vm type #9351

Merged
merged 1 commit into from
Jan 10, 2025
Merged

[release-4.18] OCPBUGS-48240: remove the types which failed by RHEL-59521 and add the new gpu vm type #9351

merged 1 commit into from
Jan 10, 2025

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #9337

/assign MayXuQQ

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jan 9, 2025
Merged
@openshift-ci openshift-ci bot requested review from andfasano and r4f4 January 9, 2025 02:25
@sadasu
Copy link
Contributor

sadasu commented Jan 9, 2025

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 9, 2025
@sadasu
Copy link
Contributor

sadasu commented Jan 9, 2025

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 9, 2025
@MayXuQQ
Copy link
Contributor

MayXuQQ commented Jan 9, 2025

@sadasu must create a JIRA to track this PR?

@MayXuQQ
Copy link
Contributor

MayXuQQ commented Jan 9, 2025

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jan 9, 2025
@openshift-cherrypick-robot openshift-cherrypick-robot force-pushed the cherry-pick-9337-to-release-4.18 branch from 6b5e053 to be93a3a Compare January 9, 2025 14:45
@MayXuQQ
Copy link
Contributor

MayXuQQ commented Jan 9, 2025

/jira cherrypick OCPBUGS-48239

@openshift-ci-robot
Copy link
Contributor

@MayXuQQ: Jira Issue OCPBUGS-48239 has been cloned as Jira Issue OCPBUGS-48240. Will retitle bug to link to clone.
/retitle OCPBUGS-48240: [release-4.18] NO-JIRA: remove the types which failed by RHEL-59521 and add the new gpu vm type

In response to this:

/jira cherrypick OCPBUGS-48239

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 changed the title [release-4.18] NO-JIRA: remove the types which failed by RHEL-59521 and add the new gpu vm type OCPBUGS-48240: [release-4.18] NO-JIRA: remove the types which failed by RHEL-59521 and add the new gpu vm type Jan 9, 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 Jan 9, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-48240, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-48239 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New instead
  • expected dependent Jira Issue OCPBUGS-48239 to target a version in 4.19.0, but it targets "4.18" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #9337

/assign MayXuQQ

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jan 9, 2025
@MayXuQQ
Copy link
Contributor

MayXuQQ commented Jan 9, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@MayXuQQ: This pull request references Jira Issue OCPBUGS-48240, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-48239 to target a version in 4.19.0, but it targets "4.19" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@MayXuQQ
Copy link
Contributor

MayXuQQ commented Jan 9, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 9, 2025
@openshift-ci-robot
Copy link
Contributor

@MayXuQQ: This pull request references Jira Issue OCPBUGS-48240, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-48239 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-48239 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

Requesting review from QA contact:
/cc @MayXuQQ

In response to this:

/jira refresh

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 requested a review from MayXuQQ January 9, 2025 15:18
@r4f4
Copy link
Contributor

r4f4 commented Jan 9, 2025

/uncc
/cc @barbacbd

@openshift-ci openshift-ci bot removed the request for review from r4f4 January 9, 2025 15:46
@openshift-ci openshift-ci bot requested a review from barbacbd January 9, 2025 15:46
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MayXuQQ, sadasu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@MayXuQQ
Copy link
Contributor

MayXuQQ commented Jan 9, 2025

@sadasu could you give me a lgtm label? thanks a lot

@sadasu
Copy link
Contributor

sadasu commented Jan 9, 2025

/retitle [release-4.18]OCPBUGS-48240: remove the types which failed by RHEL-59521 and add the new gpu vm type

@openshift-ci openshift-ci bot changed the title OCPBUGS-48240: [release-4.18] NO-JIRA: remove the types which failed by RHEL-59521 and add the new gpu vm type [release-4.18]OCPBUGS-48240: remove the types which failed by RHEL-59521 and add the new gpu vm type Jan 9, 2025
@sadasu
Copy link
Contributor

sadasu commented Jan 9, 2025

/retitle [release-4.18] OCPBUGS-48240: remove the types which failed by RHEL-59521 and add the new gpu vm type

@openshift-ci openshift-ci bot changed the title [release-4.18]OCPBUGS-48240: remove the types which failed by RHEL-59521 and add the new gpu vm type [release-4.18] OCPBUGS-48240: remove the types which failed by RHEL-59521 and add the new gpu vm type Jan 9, 2025
@sadasu
Copy link
Contributor

sadasu commented Jan 9, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@sadasu: This pull request references Jira Issue OCPBUGS-48240, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-48239 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-48239 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

Requesting review from QA contact:
/cc @MayXuQQ

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

/jira refresh

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 requested a review from MayXuQQ January 9, 2025 18:03
@sadasu
Copy link
Contributor

sadasu commented Jan 9, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 9, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 9, 2025

@openshift-cherrypick-robot: 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/e2e-ibmcloud-ovn be93a3a link false /test e2e-ibmcloud-ovn

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 06e9abd into openshift:release-4.18 Jan 10, 2025
5 of 6 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-48240: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-48240 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #9337

/assign MayXuQQ

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra
This PR has been included in build ose-installer-altinfra-container-v4.18.0-202501100110.p0.g06e9abd.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-terraform-providers
This PR has been included in build ose-installer-terraform-providers-container-v4.18.0-202501100110.p0.g06e9abd.assembly.stream.el9.
All builds following this will include this PR.

@MayXuQQ
Copy link
Contributor

MayXuQQ commented Jan 10, 2025

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link
Author

@MayXuQQ: new pull request created: #9354

In response to this:

/cherry-pick release-4.17

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 openshift-cherrypick-robot mentioned this pull request Jan 10, 2025
Open
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.18.0-202501100110.p0.g06e9abd.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.18.0-202501100110.p0.g06e9abd.assembly.stream.el9.
All builds following this will include this PR.

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

@andfasano andfasano Awaiting requested review from andfasano

@barbacbd barbacbd Awaiting requested review from barbacbd

@MayXuQQ MayXuQQ Awaiting requested review from MayXuQQ

Assignees

@sadasu sadasu

@MayXuQQ MayXuQQ

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@openshift-cherrypick-robot @sadasu @MayXuQQ @openshift-ci-robot @r4f4 @openshift-bot