openstack-origin-git should not require repeating http_proxy information
Bug #1472357 reported by
Mike McCracken
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Confirmed
|
Low
|
Unassigned | ||
nova-compute (Juju Charms Collection) |
Invalid
|
Low
|
Unassigned |
Bug Description
currently the nested yaml specifying repositories for openstack-
The charms should use the file ~/.juju-proxy that juju creates with shell exports for the proxy settings that juju knows about.
Changed in nova-compute (Juju Charms Collection): | |
importance: | Undecided → Low |
Changed in charm-nova-compute: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in nova-compute (Juju Charms Collection): | |
status: | Confirmed → Invalid |
To post a comment you must log in.
The reason we took this work-around route is because when http-proxy is set juju bootstrap on serverstack fails because it can't access keystone via the openstack provider. I originally thought it was a juju issue, but realized that when http_proxy is exported on my bastion 'nova list' fails because the keystone endpoint can't be found, whereas 'nova list' works fine if http_proxy isn't set. This might be something to do with the way DNS is set up on serverstack? Just a wild guess. But we need to figure that out and then I can work on this bug.