Bug 1383403 - can't upload images to glance
Summary: can't upload images to glance
Keywords:
Status: CLOSED DUPLICATE of bug 1382956
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: ---
Assignee: Ben Nemec
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-10 14:21 UTC by Ian Pilcher
Modified: 2016-10-11 13:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-11 13:49:04 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1630743 0 None None None 2016-10-10 14:21:48 UTC
OpenStack gerrit 382656 0 None None None 2016-10-10 14:23:59 UTC

Description Ian Pilcher 2016-10-10 14:21:48 UTC
Couldn't find a relevant downstream bug, and this doesn't seem to have made it into the latest puddle, so ...

All of our stable/newton jobs are failing on an error uploading the overcloud images to glance:

MissingSchema: Invalid URL 'x/v1/images/detail?limit=20': No schema supplied. Perhaps you meant http://x/v1/images/detail?limit=20?

In the debug output, I see:

uploading overcloud images to glance
Instantiating image client: <class 'glanceclient.v1.client.Client'>
Using auth plugin: token_endpoint
Using parameters {'url': 'x', 'token': '***', 'project_name': 'admin'}

So for some reason we are passing 'x' as the url. Switching to glance v2 results in the same error, except with v2 in the path.

Comment 1 Ben Nemec 2016-10-10 14:48:13 UTC
This is fixed upstream, so we should just need a new downstream build with the fix.

Comment 2 James Slagle 2016-10-11 13:47:09 UTC

*** This bug has been marked as a duplicate of bug 1382956 ***

Comment 3 James Slagle 2016-10-11 13:49:04 UTC

*** This bug has been marked as a duplicate of bug 1382956 ***


Note You need to log in before you can comment on or make changes to this bug.