Skip to content

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

Merged
merged 1 commit into from
Jun 14, 2017

Conversation

rootfs
Copy link
Contributor

@rootfs rootfs commented Jun 14, 2017

FIX #384

According to this line in Cinder, HTTP status 300 could return when blockstorage list API versions.

@jtopjian
Copy link
Contributor

@rootfs Thanks for submitting this, but there are two issues to resolve first before someone can take a look:

  1. There needs to be a corresponding Issue
  2. There needs to be links to the actual code where a 300 is being returned. We can't go by API documentation alone.

Let me know if you have any questions.

@coveralls
Copy link

coveralls commented Jun 14, 2017

Coverage Status

Coverage remained the same at 70.783% when pulling 7cc2c03 on rootfs:pagination-status into 8d5b28e on gophercloud:master.

@rootfs
Copy link
Contributor Author

rootfs commented Jun 14, 2017

@jtopjian @jrperritt

@rootfs
Copy link
Contributor Author

rootfs commented Jun 14, 2017

@jtopjian Thanks for the quick feedback, I updated the issue and the line in Cinder repo.

@jrperritt
Copy link
Contributor

@rootfs That link is just the unrendered docs you originally linked. It needs to be a link to the Cinder source code.

@jtopjian
Copy link
Contributor

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 pagination.Result the right place for this?

@rootfs
Copy link
Contributor Author

rootfs commented Jun 14, 2017

@jrperritt
Copy link
Contributor

@jtopjian

off the top of your head, is pagination.Result the right place for this

You mean pagination.Request? If so, then yes, all pagination requests flow through there.

@jtopjian
Copy link
Contributor

You mean pagination.Request?

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.

@jtopjian
Copy link
Contributor

Also, It looks like we can pull apiversions out of v1. No doubt more apiversions packages will be coming (notably with sharedfilesystems). Maybe it's best to standardize on that package located within the service directory and not a specific version directory.

@jtopjian
Copy link
Contributor

@rootfs Thanks for catching this error and submitting the fix 😄

@jtopjian jtopjian merged commit ed590d9 into gophercloud:master Jun 14, 2017
@rootfs
Copy link
Contributor Author

rootfs commented Jun 14, 2017

Thank you @jtopjian @jrperritt !

pospispa pushed a commit to pospispa/origin that referenced this pull request Sep 13, 2017
…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
openshift-merge-robot added a commit to openshift/origin that referenced this pull request Sep 18, 2017
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants