Skip to content

OCPBUGS-74986: Revendor CAPO#152

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.18from
shiftstack:revendor-capo-4.18
Feb 5, 2026
Merged

OCPBUGS-74986: Revendor CAPO#152
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.18from
shiftstack:revendor-capo-4.18

Conversation

@mandre
Copy link
Member

@mandre mandre commented Feb 3, 2026

Re-vendor CAPO to get fix for deleting instances when OpenStack has
a policy in place that prevents detaching the primary interface.

go get sigs.k8s.io/cluster-api-provider-openstack@release-0.9
go mod tidy
go mod vendor

pierreprinetti and others added 2 commits February 3, 2026 11:23
Previously, the gitignore instruction to ignore generated files applied
to the `/vendor` directory, effectively removing files from vendored
dependencies.
Re-vendor CAPO to get fix for deleting instances when OpenStack has
a policy in place that prevents detaching the primary interface.

    go get sigs.k8s.io/cluster-api-provider-openstack@release-0.9
    go mod tidy
    go mod vendor
@mandre
Copy link
Member Author

mandre commented Feb 3, 2026

/jira cherrypick OCPBUGS-74586

@openshift-ci-robot
Copy link
Contributor

@mandre: Jira Issue OCPBUGS-74586 has been cloned as Jira Issue OCPBUGS-74986. Will retitle bug to link to clone.
/retitle OCPBUGS-74986: Revendor CAPO

Details

In response to this:

/jira cherrypick OCPBUGS-74586

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 Revendor CAPO OCPBUGS-74986: Revendor CAPO Feb 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mandre

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 3, 2026
@openshift-ci-robot
Copy link
Contributor

@mandre: This pull request references Jira Issue OCPBUGS-74986, which is invalid:

  • expected dependent Jira Issue OCPBUGS-74586 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

Details

In response to this:

Re-vendor CAPO to get fix for deleting instances when OpenStack has
a policy in place that prevents detaching the primary interface.

go get sigs.k8s.io/cluster-api-provider-openstack@release-0.9
go mod tidy
go mod vendor

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 Feb 3, 2026
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

@mandre: all tests passed!

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.

@mandre
Copy link
Member Author

mandre commented Feb 4, 2026

/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 Feb 4, 2026
@openshift-ci-robot
Copy link
Contributor

@mandre: This pull request references Jira Issue OCPBUGS-74986, 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.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-74586 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-74586 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (imatza@redhat.com), skipping review request.

Details

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.

@mandre
Copy link
Member Author

mandre commented Feb 4, 2026

/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 Feb 4, 2026
@mandre
Copy link
Member Author

mandre commented Feb 4, 2026

/verified later @dlaw4608

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Feb 4, 2026
@openshift-ci-robot
Copy link
Contributor

@mandre: This PR has been marked to be verified later by @dlaw4608.

Details

In response to this:

/verified later @dlaw4608

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.

@eshulman2
Copy link
Member

LGTM

@eshulman2
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 5, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 5a95c50 into openshift:release-4.18 Feb 5, 2026
10 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the revendor-capo-4.18 branch February 5, 2026 10:43
@openshift-ci-robot
Copy link
Contributor

@mandre: Jira Issue OCPBUGS-74986: All pull requests linked via external trackers have merged:

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-74986 has been moved to the MODIFIED state.

Details

In response to this:

Re-vendor CAPO to get fix for deleting instances when OpenStack has
a policy in place that prevents detaching the primary interface.

go get sigs.k8s.io/cluster-api-provider-openstack@release-0.9
go mod tidy
go mod vendor

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.

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. 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. verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants