Cinder list with pagination contains wrong scheme for "next" link in case of SSL endpoints
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Fix Committed
|
Medium
|
Yuriy Nesenenko | |||
7.0.x |
Fix Released
|
Medium
|
Denis Puchkin | |||
8.0.x |
Fix Released
|
Medium
|
Denis Puchkin | |||
9.x |
Fix Released
|
High
|
Yuriy Nesenenko |
Bug Description
Detailed bug description:
we have an environment where we have endpoints for our services SSL based(https), listening behind nginx. Now, most tests have been passing fine without any issue , however except the "tempest.
Traceback (most recent call last):
File "tempest/
self.
File "tempest/
response.
File "/var/lib/
self.
File "/var/lib/
raise mismatch_error
testtools.
reference = 'http://
actual = 'https:/
here the only minute difference is of http and https.
A better debug with output is shown below where i print them in the code where response and body are received :
response:
{'status': '200', 'content-length': '552', 'content-location': 'https:/
Body:
{u'volumes_links': [{u'href': u'http://
In above output, you can clearly see http and https in both fields.
Steps to reproduce:
to reproduce, its simple, to have https based environment, and see if this test makes through.
Expected results:
href field contains link with https
Actual result:
href field contains link with http
Reproducibility:
Every time
Related bugs:
https:/
https:/
Changed in mos: | |
milestone: | 10.0 → 7.0-updates |
tags: | added: customer-found sla2 |
Changed in mos: | |
assignee: | MOS Cinder (mos-cinder) → Yuriy Nesenenko (ynesenenko) |
tags: | added: cinder swarm-blocker |
tags: | added: on-verification |
tags: | added: on-verification |
The bug was reproduced in mitaka-9.0