openstack-origin-git should not require repeating http_proxy information

Bug #1472357 reported by Mike McCracken
6
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-origin-git requires the user to repeat proxy information that must be already set in the juju environment.

The charms should use the file ~/.juju-proxy that juju creates with shell exports for the proxy settings that juju knows about.

Revision history for this message
Corey Bryant (corey.bryant) wrote :

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.

Changed in nova-compute (Juju Charms Collection):
status: New → Confirmed
Revision history for this message
Mike McCracken (mikemc) wrote : Re: [Bug 1472357] Re: openstack-origin-git should not require repeating http_proxy information

We work around this in the openstack installer by using the NO_PROXY env
var and listing all the IPs for the various endpoints that will need to
talk to each other. I think we might actually list the entire /24 or so (it
only takes IPs, not ranges, so you have to write them all out)

On Thu, Jul 23, 2015 at 1:04 PM, Corey Bryant <email address hidden>
wrote:

> 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.
>
> ** Changed in: nova-compute (Juju Charms Collection)
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1472357
>
> Title:
> openstack-origin-git should not require repeating http_proxy
> information
>
> Status in nova-compute package in Juju Charms Collection:
> Confirmed
>
> Bug description:
> currently the nested yaml specifying repositories for openstack-
> origin-git requires the user to repeat proxy information that must be
> already set in the juju environment.
>
> The charms should use the file ~/.juju-proxy that juju creates with
> shell exports for the proxy settings that juju knows about.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/charms/+source/nova-compute/+bug/1472357/+subscriptions
>

Liam Young (gnuoy)
Changed in nova-compute (Juju Charms Collection):
importance: Undecided → Low
James Page (james-page)
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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.