bump the version of gophercloud#11830
Conversation
Since the v1.19.0 release of kOps the OpenStack integration has been broken because gophercloud made a change to start escaping all path names for files stored in swift. kOps used a file with a slash in it which was getting escaped and then not handled correctly. This has been fixed in upstream gophercloud with gophercloud/gophercloud#2160 which was included in gophercloud v0.18.0. Bump is for issue kubernetes#9933. (cherry picked from commit 80da992)
|
Hi @cardoe. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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/test-infra repository. |
|
/ok-to-test |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Since the v1.19.0 release of kOps the OpenStack integration has been
broken because gophercloud made a change to start escaping all path
names for files stored in swift. kOps used a file with a slash in it
which was getting escaped and then not handled correctly. This has been
fixed in upstream gophercloud with gophercloud/gophercloud#2160 which
was included in gophercloud v0.18.0. Bump is for issue #9933. This is a
cherry-pick of #11788 to 1.21.
(cherry picked from commit 80da992)