[openstack-dev] [glance][rally] Disabling Glance Testing in Rally gates
Abhishek.Kekane at nttdata.com
Thu Jul 13 09:15:14 UTC 2017
Someone has reported this issue in glance recently.
Please refer, https://bugs.launchpad.net/glance/+bug/1703856
I think it is same kind of failure which Andrey was mentioning.
As mentioned in the bug temporary solution is to enable the v1 api using the v1 parameter, --location instead of using --file. But this will not be applicable to rally scenarios I guess.
I will spend some time to understand the failure cause.
From: Andrey Kurilin [mailto:andr.kurilin at gmail.com]
Sent: Thursday, July 13, 2017 2:25 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [glance][rally] Disabling Glance Testing in Rally gates
2017-07-13 11:16 GMT+03:00 Flavio Percoco <flavio at redhat.com<mailto:flavio at redhat.com>>:
On 13/07/17 00:56 -0700, Boris Pavlovic wrote:
Unfortunately what was discussed in other thread (situation in glance is
Glance stopped working and Rally team is forced to disable checking of it
in Rally gates.
P.S. Seems like this patch is casing the problems:
Has this been brought up to the Glance team? Or is this email meant to do that?
FWIW, the switch to uwsgi is a community goal and not so much a Glance thing.
Would you mind elaborating on what exactly is failing and how the glance team
I understand that switching to uwsgi is a community goal, but we didn't have any problems with Glance for years until now.
As from IRC logs:
> HTTPBadGateway: 502 Bad Gateway: Bad Gateway: The proxy server received an invalid: response from an upstream server.: Apache/2.4.18 (Ubuntu) Server at 184.108.40.206 Port 80 (HTTP 502)
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStackemail@example.com?subject:unsubscribe>
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev