-
Notifications
You must be signed in to change notification settings - Fork 42.1k
Automated cherry pick of #47602 upstream release 1.7 #49026
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
Automated cherry pick of #47602 upstream release 1.7 #49026
Conversation
…ng Cinder v1/v2 API versions won't break Signed-off-by: Huamin Chen <[email protected]>
|
@idvoretskyi @dchen1107 can you approve? thanks! |
|
This is great to have. I don't have karma to add cherrypick-approved label. +1 from me for backporting this. |
|
cc @wojtek-t who's the patch branch manager. Also please follow the cherrypick process (https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md#propose-a-cherry-pick), which requires labels to be added to master branch PR. |
|
/approve @wojtek-t this is ok for cherry pick from storage SIG -- fixes a big regression in 1.7 with Openstack/Cinder |
|
/approve no-issue |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rootfs, saad-ali, wojtek-t Associated issue: 47602 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/test pull-kubernetes-e2e-kops-aws |
|
/test pull-kubernetes-e2e-gce-etcd3 |
3 similar comments
|
/test pull-kubernetes-e2e-gce-etcd3 |
|
/test pull-kubernetes-e2e-gce-etcd3 |
|
/test pull-kubernetes-e2e-gce-etcd3 |
|
/retest |
1 similar comment
|
/retest |
|
/test pull-kubernetes-federation-e2e-gce |
1 similar comment
|
/test pull-kubernetes-federation-e2e-gce |
|
Automatic merge from submit-queue |
Cherry pick of #47602 on release-1.7.
#47602 : rebase gophercloud to support HTTP status 300 in pagination, so listingng Cinder v1/v2 API versions won't break