Skip to content

Merge https://github.com/kubernetes/cloud-provider-openstack:release-1.33 into release-4.20 #368

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
Open
shiftstack-merge-bot wants to merge 5 commits into
base: release-4.20
Choose a base branch
from
Open

Merge https://github.com/kubernetes/cloud-provider-openstack:release-1.33 into release-4.20 #368

shiftstack-merge-bot wants to merge 5 commits into from

Conversation

@shiftstack-merge-bot
Copy link

@shiftstack-merge-bot shiftstack-merge-bot bot commented Jan 22, 2026

No description provided.

@k8s-infra-cherrypick-robot @zetaab
add debug logging on deployment failure, update nfs image (kubernetes…
0e0d211 
…#3051)

Co-authored-by: Jesse Haka <haka.jesse@gmail.com>
@k8s-infra-cherrypick-robot @eshulman2
Allow manila e2e testing with DHSS=true (kubernetes#3049)
e9b49ae 
When using manila DHSS=true the network needs to be specified to allow
using/creating the share. To allow e2e testing in a DHSS=true env I
added an option to specify network via an environment variable keeping
backward compatibility while allowing testing with DHSS=true

Co-authored-by: eshulman2 <ellashulman1@gmail.com>
@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jan 22, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 22, 2026

Hi @shiftstack-merge-bot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@stephenfin
Copy link

stephenfin commented Jan 22, 2026

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 22, 2026
@k8s-infra-cherrypick-robot @kayrus
[release-1.33] tests: bump devstack to stable/2025.2 (kubernetes#3056)
63374c5 
* tests: bump devstack to stable/2025.2

* tests: show loadbalancer tags in raw format

---------

Co-authored-by: pýrus <kayrus@users.noreply.github.com>
@k8s-infra-cherrypick-robot @kayrus
tests: split kubectl download task into multiple with retries (kubern…
add1e66 
…etes#3061)

Co-authored-by: pýrus <kayrus@users.noreply.github.com>
@eshulman2
Copy link
Member

eshulman2 commented Jan 25, 2026

/test e2e-openstack

@eshulman2
Copy link
Member

eshulman2 commented Jan 27, 2026

/test security

@openshift-ci
Copy link

openshift-ci bot commented Jan 27, 2026

@shiftstack-merge-bot[bot]: 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/security 70f53d4 link false /test security

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.

@stephenfin
Copy link

stephenfin commented Jan 27, 2026

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

stephenfin commented Jan 27, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: shiftstack-merge-bot[bot], stephenfin

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

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

Reviewers

@mandre mandre Awaiting requested review from mandre

@pierreprinetti pierreprinetti Awaiting requested review from pierreprinetti

Assignees

@stephenfin stephenfin

@itzikb-redhat itzikb-redhat

@imatza-rh imatza-rh

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. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@stephenfin @eshulman2 @itzikb-redhat @imatza-rh @k8s-infra-cherrypick-robot