-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add blockstorage version for openstack #5776
Add blockstorage version for openstack #5776
Conversation
Can one of the admins verify this patch?
|
Hi @pearj. 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 I understand the commands that are listed here. 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. |
This is related to kubernetes/website#5925 |
Can one of the admins verify this patch?
|
@@ -251,6 +251,9 @@ openshift_master_identity_providers=[{'name': 'htpasswd_auth', 'login': 'true', | |||
#openshift_cloudprovider_openstack_region=region | |||
#openshift_cloudprovider_openstack_lb_subnet_id=subnet_id | |||
# | |||
# Note: If you're getting a "BS API version autodetection failed" when provisioning cinder volumes you may need this setting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this note could be a little clearer.
Let's include the affected versions as mentioned in kubernetes/website#5925
Or perhaps we should wait to see what the approved text is from kubernetes, if that patch ships soon.
/ok-to-test @pearj |
The referenced PR merged upstream. /lgtm /test upgrade |
/test upgrade |
For what it’s worth I run my OpenStack with port based endpoints, so in theory according to that new k8s doco, I should be unaffected, yet I was. When I looked at the cinder go files, I can see that in k8s 1.7 there is some auto detection, but nothing in 1.6. So that’s why I left my comment a bit vague. Otherwise, it sounds like it might be:
I haven’t tried the RC of OpenShift 3.7, so I don’t actually know if it is needed in 3.7 or not. |
@pearj Thanks for the clarification. Yeah, I think the message provides some information that will lead users to the right choice. |
/test upgrade |
3 similar comments
/test upgrade |
/test upgrade |
/test upgrade |
@pearj: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
Can we get this cherry-picked to the release-3.7 branch too? I've discovered this is broken for 3.7 as well. Should I submit a new pull request? |
/cherrypick release-3.7 |
@michaelgugino: #5776 failed to apply on top of branch "release-3.7":
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 prepared a new pull request, #6611, for OpenShift 3.7 |
When running on OpenStack pike using https://github.com/openshift/openshift-ansible-contrib/tree/master/playbooks/provisioning/openstack with OpenShift Origin 3.6 I found that when trying to use/provision cinder-volumes I got a "BS API version autodetection failed" error.
Specifying the
bs-version=v2
in openstack.conf made the error go away.