-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
use availability_zone instead of availability (update godep for gophercloud) #44082
Conversation
Hi @zetaab. 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 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/test-infra repository. I understand the commands that are listed here. |
Hi @zetaab, It looks like this was added to gophercloud here: gophercloud/gophercloud@b06120d We could update the godep to pull this change in. Information on updating godeps is here: https://github.com/kubernetes/community/blob/master/contributors/devel/godep.md |
is that correctly updated deps? @cblecker I updated whole gophercloud/gophercloud |
You actually need to use the Godep tool to do this kind of update, as it tracks when the updates were done and the hashes of those updates. Directions and details here: https://github.com/kubernetes/community/blob/master/contributors/devel/godep.md |
I tried to follow those instructions but it does not work, maybe someone who have done this before can do it?
|
@cblecker any ideas? |
Oh hmm.. try using |
I just tried this locally, and it seems to have worked. If you wouldn't mind testing on your environment to see if that allows you to update the godep, that would be great. |
@cblecker your instructions works pretty well, if those files are now OK :) The only thing which did not work is verify godeps % ./hack/verify-godeps.sh i tried also execute godep update and rerun it, but it did not help |
Ah! Are you working off a git branch, or just a clone of master? |
@k8s-bot ok to test |
I was working in that fixzone2 branch git checkout master I have no idea why those tests fail :) |
@cblecker thanks for helping 👍 |
@k8s-bot ok to test |
@idvoretskyi Can you add the sig/openstack label please? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dchen1107, pospispa, zetaab
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@dchen1107 @zetaab Does this need a release note? Only piece that is blocking merge here. |
well, imo someone (who have access) could add release-note-none or release-note and remove release-note-label-needed and do-not-merge? This is basically godep update for gophercloud, and if i check previous changelog items, some of these are there. So if we just add release-note its fine for me(its added to changelog with that i think?). |
Release notes are needed when there is a breaking change, or a notable change in functionality (for better or worse). In this case, I this looks like just a bug fix. Will still need @dchen1107 to remove the |
@cblecker: you can only set release notes if you are the author or an assignee. In response to this:
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/test-infra repository. I understand the commands that are listed here. |
/assign |
/release-note-none |
@k8s-bot non-cri e2e test this |
1 similar comment
@k8s-bot non-cri e2e test this |
Automatic merge from submit-queue |
cc @kubernetes/sig-openstack-bugs |
This is "backport" of Kubernetes PR #44082 (kubernetes/kubernetes#44082). Actually, the github.com/gophercloud/gophercloud library version is bumped up to a version that contains the availability zone fix. The problem is described in Bugzilla #1444828 (https://bugzilla.redhat.com/show_bug.cgi?id=1444828). The problem was introduced into Kubernetes 1.6 and fixed in Kubernetes 1.7. That's why the fix is "backported" into OpenShift 3.6.
This is "backport" of Kubernetes PR #44082 (kubernetes/kubernetes#44082). Actually, the github.com/gophercloud/gophercloud library version is bumped up to a version that contains the availability zone fix. The problem is described in Bugzilla #1444828 (https://bugzilla.redhat.com/show_bug.cgi?id=1444828). The problem was introduced into Kubernetes 1.6 and fixed in Kubernetes 1.7. That's why the fix is "backported" into OpenShift 3.6.
This is "backport" of Kubernetes PR #44082 (kubernetes/kubernetes#44082). Actually, the github.com/gophercloud/gophercloud library version is bumped up to a version that contains the availability zone fix. The problem is described in Bugzilla #1444828 (https://bugzilla.redhat.com/show_bug.cgi?id=1444828). The problem was introduced into Kubernetes 1.6 and fixed in Kubernetes 1.7. That's why the fix is "backported" into OpenShift 3.6.
…0898813696af0 This is first part of the "backport" of Kubernetes PR #44082 (kubernetes/kubernetes#44082). Actually, the github.com/gophercloud/gophercloud library version is bumped up to a version that contains the availability zone fix. The problem is described in Bugzilla #1444828 (https://bugzilla.redhat.com/show_bug.cgi?id=1444828). The problem was introduced into Kubernetes 1.6 and fixed in Kubernetes 1.7. That's why the fix is "backported" into OpenShift 3.6.
This is second and last part of the "backport" of Kubernetes PR #44082 (kubernetes/kubernetes#44082). Actually, the github.com/gophercloud/gophercloud library version is bumped up to a version that contains the availability zone fix. The problem is described in Bugzilla #1444828 (https://bugzilla.redhat.com/show_bug.cgi?id=1444828). The problem was introduced into Kubernetes 1.6 and fixed in Kubernetes 1.7. That's why the fix is "backported" into OpenShift 3.6.
Automatic merge from submit-queue use availability_zone instead of availability (update godep for gophercloud) **What this PR does / why we need it**: there is typo in json variable name **Which issue this PR fixes**: fixes kubernetes#44032 **Special notes for your reviewer**:our openstack environment region name is not nova, so I tested this and it works now All cinder blockstorages are using variable name availability_zone instead of availability. Docs: v3: https://developer.openstack.org/api-ref/block-storage/v3/index.html?expanded=create-a-volume-detail#create-a-volume v2: https://developer.openstack.org/api-ref/block-storage/v2/index.html?expanded=create-volume-detail#create-volume I could not find v1 documentation anymore from openstack pages. However, https://developer.rackspace.com/docs/cloud-block-storage/v1/api-reference/cbs-volumes-operations/#create-a-volume documentation says also availability_zone is the correct one. Like mentioned in kubernetes#44032 (comment) openstack CLI is using availability_zone
What this PR does / why we need it: there is typo in json variable name
Which issue this PR fixes: fixes #44032
Special notes for your reviewer:our openstack environment region name is not nova, so I tested this and it works now
All cinder blockstorages are using variable name availability_zone instead of availability. Docs:
v3:
https://developer.openstack.org/api-ref/block-storage/v3/index.html?expanded=create-a-volume-detail#create-a-volume
v2:
https://developer.openstack.org/api-ref/block-storage/v2/index.html?expanded=create-volume-detail#create-volume
I could not find v1 documentation anymore from openstack pages. However, https://developer.rackspace.com/docs/cloud-block-storage/v1/api-reference/cbs-volumes-operations/#create-a-volume documentation says also availability_zone is the correct one.
Like mentioned in #44032 (comment) openstack CLI is using availability_zone