Skip to content

OCPBUGS-77941: Remove cluster-api-provider-libvirt builds#9300

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-eng:openshift-4.22from
sdodson:OCPBUGS-77941
Mar 30, 2026
Merged

OCPBUGS-77941: Remove cluster-api-provider-libvirt builds#9300
openshift-merge-bot[bot] merged 1 commit intoopenshift-eng:openshift-4.22from
sdodson:OCPBUGS-77941

Conversation

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 6, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@sdodson: This pull request references Jira Issue OCPBUGS-77941, 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 Jira Issue OCPBUGS-77941 to depend on a bug targeting a version in 4.23.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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.

Details

In response to this:

Waiting on

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.

@adobes1
Copy link
Copy Markdown
Contributor

adobes1 commented Mar 11, 2026

/cherry-pick openshift-4.23
/cherry-pick openshift-5.0

@openshift-cherrypick-robot
Copy link
Copy Markdown

@adobes1: once the present PR merges, I will cherry-pick it on top of openshift-4.23, openshift-5.0 in new PRs and assign them to you.

Details

In response to this:

/cherry-pick openshift-4.23
/cherry-pick openshift-5.0

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.

@adobes1
Copy link
Copy Markdown
Contributor

adobes1 commented Mar 13, 2026

/retest

@sdodson
Copy link
Copy Markdown
Author

sdodson commented Mar 29, 2026

@adobes1 openshift/release has been updated to remove these builds, anything else we need to do before we make this change here?

@adobes1
Copy link
Copy Markdown
Contributor

adobes1 commented Mar 30, 2026

@sdodson I don't think there's anything else
oc adm release new -n ocp --dry-run --reference-mode=source --from-image-stream 4.22-art-latest also succeeded so we should be good to merge this

@adobes1
Copy link
Copy Markdown
Contributor

adobes1 commented Mar 30, 2026

/unhold
/lgtm
/approve

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 30, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 30, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adobes1

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

The pull request process is described here

Details 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 Mar 30, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 30, 2026

@sdodson: 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/art-pre-commit-check 42a6c76 link false /test art-pre-commit-check

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.

@adobes1
Copy link
Copy Markdown
Contributor

adobes1 commented Mar 30, 2026

/test art-konflux-delivery-repo-check

@openshift-merge-bot openshift-merge-bot Bot merged commit a144ba2 into openshift-eng:openshift-4.22 Mar 30, 2026
3 of 4 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@sdodson: Jira Issue OCPBUGS-77941 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

Details

In response to this:

Waiting on

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-cherrypick-robot
Copy link
Copy Markdown

@adobes1: new pull request created: #9701

Details

In response to this:

/cherry-pick openshift-4.23
/cherry-pick openshift-5.0

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
Copy link
Copy Markdown

@adobes1: new pull request created: #9702

Details

In response to this:

/cherry-pick openshift-4.23
/cherry-pick openshift-5.0

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

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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.

4 participants