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.

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

[release-4.17] USHIFT-3780: Fix cleanup-all option in manage_hypervisor_config.sh #3747

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #3744

/assign ggiguash

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 9, 2024

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-3780

In response to this:

This is an automated cherry-pick of #3744

/assign ggiguash

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.

@ggiguash
Copy link
Contributor

ggiguash commented Aug 9, 2024

/label backport-risk-assessed
/label jira/valid-bug
/lgtm
/cherry-pick-approved

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. labels Aug 9, 2024
Copy link
Contributor

openshift-ci bot commented Aug 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, openshift-cherrypick-robot

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

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

ggiguash commented Aug 9, 2024

/jira refresh

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

openshift-ci-robot commented Aug 9, 2024

@ggiguash: This pull request references USHIFT-3780 which is a valid jira issue.

Retaining the jira/valid-bug label as it was manually added.

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.

@ggiguash
Copy link
Contributor

ggiguash commented Aug 9, 2024

/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 Aug 9, 2024
@ggiguash
Copy link
Contributor

ggiguash commented Aug 9, 2024

/test ?

Copy link
Contributor

openshift-ci bot commented Aug 9, 2024

@ggiguash: The following commands are available to trigger required jobs:

  • /test footprint-and-performance
  • /test images
  • /test metal-bootc-periodic-test
  • /test metal-bootc-periodic-test-arm
  • /test metal-bootc-test
  • /test metal-bootc-test-arm
  • /test metal-periodic-test
  • /test metal-periodic-test-arm
  • /test microshift-metal-cache
  • /test microshift-metal-cache-arm
  • /test microshift-metal-tests
  • /test microshift-metal-tests-arm
  • /test ocp-conformance-rhel-eus
  • /test ocp-conformance-rhel-eus-arm
  • /test ocp-full-conformance-rhel-eus
  • /test test-rpm
  • /test test-unit
  • /test verify

The following commands are available to trigger optional jobs:

  • /test test-rebase

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-microshift-release-4.17-images
  • pull-ci-openshift-microshift-release-4.17-metal-bootc-periodic-test
  • pull-ci-openshift-microshift-release-4.17-metal-bootc-periodic-test-arm
  • pull-ci-openshift-microshift-release-4.17-metal-bootc-test
  • pull-ci-openshift-microshift-release-4.17-metal-bootc-test-arm
  • pull-ci-openshift-microshift-release-4.17-metal-periodic-test
  • pull-ci-openshift-microshift-release-4.17-metal-periodic-test-arm
  • pull-ci-openshift-microshift-release-4.17-microshift-metal-tests
  • pull-ci-openshift-microshift-release-4.17-microshift-metal-tests-arm
  • pull-ci-openshift-microshift-release-4.17-test-unit
  • pull-ci-openshift-microshift-release-4.17-verify

In response to this:

/test ?

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.

@ggiguash
Copy link
Contributor

ggiguash commented Aug 9, 2024

/test microshift-metal-cache
/test microshift-metal-cache-arm

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ef76b69 and 2 for PR HEAD 39451ad in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD e264c90 and 1 for PR HEAD 39451ad in total

@ggiguash
Copy link
Contributor

/test metal-periodic-test-arm

Copy link
Contributor

openshift-ci bot commented Aug 10, 2024

@openshift-cherrypick-robot: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit f8b77fc into openshift:release-4.17 Aug 10, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging this pull request may close these issues.

3 participants