Skip to content

[release-4.18] OCPBUGS-51263: Drop oVirt support #1333

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

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1331

/assign JoelSpeed

/cherrypick release-4.17 release-4.16 release-4.15 release-4.14

@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-51042 has been cloned as Jira Issue OCPBUGS-51263. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-51263: Drop oVirt support

In response to this:

This is an automated cherry-pick of #1331

/assign JoelSpeed

/cherrypick release-4.17 release-4.16 release-4.15 release-4.14

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.

@JoelSpeed
Copy link
Contributor

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot changed the title [release-4.18] OCPBUGS-51042: Drop oVirt support [release-4.18] OCPBUGS-51263: Drop oVirt support Feb 25, 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 Feb 25, 2025
@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 Feb 25, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 25, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-51263, 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-51042 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-51042 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 @sunzhaohua2

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 #1331

/assign JoelSpeed

/cherrypick release-4.17 release-4.16 release-4.15 release-4.14

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 lgtm Indicates that a PR is ready to be merged. label Feb 25, 2025
Copy link
Contributor

openshift-ci bot commented Feb 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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 Feb 25, 2025
Copy link
Contributor

openshift-ci bot commented Feb 25, 2025

@openshift-cherrypick-robot: The following tests 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-vsphere-operator 3ccd777 link false /test e2e-vsphere-operator
ci/prow/okd-scos-e2e-aws-ovn 3ccd777 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-vsphere-ovn-multi-vcenter 3ccd777 link false /test e2e-vsphere-ovn-multi-vcenter
ci/prow/e2e-vsphere-ovn-serial 3ccd777 link false /test e2e-vsphere-ovn-serial
ci/prow/e2e-nutanix 3ccd777 link false /test e2e-nutanix
ci/prow/e2e-metal-ipi-ovn-ipv6 3ccd777 link false /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-vsphere-ovn-upgrade 3ccd777 link false /test e2e-vsphere-ovn-upgrade
ci/prow/e2e-metal-ipi-ovn-dualstack 3ccd777 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-vsphere-ovn 3ccd777 link false /test e2e-vsphere-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.

@JoelSpeed
Copy link
Contributor

@sunzhaohua2 Are you able to add the cherry-pick approval here please?

@sunzhaohua2
Copy link
Contributor

/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 Feb 27, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 1df65ac into openshift:release-4.18 Feb 27, 2025
20 of 29 checks passed
@openshift-ci-robot
Copy link
Contributor

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

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

In response to this:

This is an automated cherry-pick of #1331

/assign JoelSpeed

/cherrypick release-4.17 release-4.16 release-4.15 release-4.14

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
Author

@openshift-cherrypick-robot: #1333 failed to apply on top of branch "release-4.17":

Applying: Drop oVirt support
Using index info to reconstruct a base tree...
M	install/0000_30_machine-api-operator_00_credentials-request.yaml
M	pkg/operator/operator_test.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/operator/operator_test.go
CONFLICT (content): Merge conflict in pkg/operator/operator_test.go
Auto-merging install/0000_30_machine-api-operator_00_credentials-request.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Drop oVirt support

In response to this:

This is an automated cherry-pick of #1331

/assign JoelSpeed

/cherrypick release-4.17 release-4.16 release-4.15 release-4.14

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

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-api-operator
This PR has been included in build ose-machine-api-operator-container-v4.18.0-202502270435.p0.g1df65ac.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
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.

None yet

7 participants