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

regression 1.6 => 1.7 - cinder plugin #53737

Closed
mmaquevice opened this Issue Oct 11, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@mmaquevice
Contributor

mmaquevice commented Oct 11, 2017

Maybe there is a regression concerning the openstack provider plugin for cinder.

I manage to create a PVC in 1.6 (and the volume associated in openstack).

However in 1.7, I go the following error (with the same configuration):

E1011 16:13:44.309318       5 openstack_volumes.go:320] Failed to create a 3 GB volume: Invalid request due to incorrect syntax or missing required parameters.

I1011 16:13:44.309411       5 cinder_util.go:207] Error creating cinder volume: Invalid request due to incorrect syntax or missing required parameters.

I1011 16:13:44.309458       5 pv_controller.go:1331] failed to provision volume for claim "default/my-persistent-volume-claim" with StorageClass "standard": Invalid request due to incorrect syntax or missing required parameters.
@mmaquevice

This comment has been minimized.

Show comment
Hide comment
@mmaquevice

mmaquevice Oct 11, 2017

Contributor

/sig openstack

Contributor

mmaquevice commented Oct 11, 2017

/sig openstack

@FengyunPan

This comment has been minimized.

Show comment
Hide comment
@FengyunPan

FengyunPan Oct 16, 2017

/sig storage

Invalid request due to incorrect syntax or missing required parameters.

@mmaquevice The log is hard to get the reason of this issuse. SO can you give some log about it from Cinder?

FengyunPan commented Oct 16, 2017

/sig storage

Invalid request due to incorrect syntax or missing required parameters.

@mmaquevice The log is hard to get the reason of this issuse. SO can you give some log about it from Cinder?

@mmaquevice

This comment has been minimized.

Show comment
Hide comment
@mmaquevice

mmaquevice Oct 16, 2017

Contributor

Thanks for your reply @FengyunPan
Indeed it is hard to debug with this log. Unfortunately I don't have access to server logs. I have tried with another openstack cloud provider and it works great.
It does not resolve the issue but I guess it is due to a specific implementation of openstack, I close the bug.

Contributor

mmaquevice commented Oct 16, 2017

Thanks for your reply @FengyunPan
Indeed it is hard to debug with this log. Unfortunately I don't have access to server logs. I have tried with another openstack cloud provider and it works great.
It does not resolve the issue but I guess it is due to a specific implementation of openstack, I close the bug.

@mmaquevice mmaquevice closed this Oct 16, 2017

@jianglingxia

This comment has been minimized.

Show comment
Hide comment
@jianglingxia

jianglingxia Nov 22, 2017

Contributor

have you upgrade especially from non-OpenStack Cloud Provider to OpenStack Cloud Provider?
the issue is 1.6 with OpenStack Cloud Provider upgrade 1.7 with OpenStack Cloud Provider? thanks

Contributor

jianglingxia commented Nov 22, 2017

have you upgrade especially from non-OpenStack Cloud Provider to OpenStack Cloud Provider?
the issue is 1.6 with OpenStack Cloud Provider upgrade 1.7 with OpenStack Cloud Provider? thanks

@mmaquevice

This comment has been minimized.

Show comment
Hide comment
@mmaquevice

mmaquevice Nov 22, 2017

Contributor

The issue was from/to the same OpenStack Cloud Provider.

Contributor

mmaquevice commented Nov 22, 2017

The issue was from/to the same OpenStack Cloud Provider.

@jianglingxia

This comment has been minimized.

Show comment
Hide comment
@jianglingxia

jianglingxia Nov 22, 2017

Contributor

do you know the follow question?
1、why config the OpenStack Cloud Provider ,the k8s use the nodename instead of ip?
2、if the nodename has two same and What to do?I read the code and no place to validate the same nodename.
thanks for reply

Contributor

jianglingxia commented Nov 22, 2017

do you know the follow question?
1、why config the OpenStack Cloud Provider ,the k8s use the nodename instead of ip?
2、if the nodename has two same and What to do?I read the code and no place to validate the same nodename.
thanks for reply

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