-
Notifications
You must be signed in to change notification settings - Fork 555
support HTTP status 300 in pagination #383
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
Conversation
Signed-off-by: Huamin Chen <[email protected]>
@rootfs Thanks for submitting this, but there are two issues to resolve first before someone can take a look:
Let me know if you have any questions. |
@jtopjian Thanks for the quick feedback, I updated the issue and the line in Cinder repo. |
@rootfs That link is just the unrendered docs you originally linked. It needs to be a link to the Cinder source code. |
To save @rootfs some time digging, here's the appropriate link: https://github.com/openstack/cinder/blob/3f8466b712d7a0b300c07d1d215c0dd256a769f7/cinder/api/versions.py#L125 @jrperritt off the top of your head, is |
You mean |
Yes - that one :) OK, thanks. That saves me some time. This looks good to me. A 300 result is certainly possible. I'm going to go ahead and merge. |
Also, It looks like we can pull |
@rootfs Thanks for catching this error and submitting the fix 😄 |
Thank you @jtopjian @jrperritt ! |
…96155e6579e78 Automatic detection of Cinder API version doesn't work. The problem is described in Bugzilla #14907688 (https://bugzilla.redhat.com/show_bug.cgi?id=1490768). The problem is in the gophercloud library that doesn't support HTTP code 300 in pagination. This problem is fixed in PR: gophercloud/gophercloud#383 That's why the gophercloud library version is bumped up to ed590d9afe113c6107cd60717b196155e6579e78
…gzilla1490768-support-HTTP-300-response-in-pagination Automatic merge from submit-queue (batch tested with PRs 15834, 16321, 16353, 15298, 15433) bump(github.com/gophercloud/gophercloud): ed590d9afe113c6107cd60717b196155e6579e78 Automatic detection of Cinder API version doesn't work. The problem is described in Bugzilla #14907688 (https://bugzilla.redhat.com/show_bug.cgi?id=1490768). The problem is in the gophercloud library that doesn't support HTTP code 300 in pagination. This problem is fixed in PR: gophercloud/gophercloud#383 That's why the gophercloud library version is bumped up to ed590d9afe113c6107cd60717b196155e6579e78 fix https://bugzilla.redhat.com/show_bug.cgi?id=1490768 @rootfs PTAL
FIX #384
According to this line in Cinder, HTTP status 300 could return when blockstorage list API versions.