odl-controller should use juju's proxy settings
Bug #1514529 reported by
Andreas Hasenack
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack odl-controller charm |
Triaged
|
Medium
|
Unassigned | ||
odl-controller (Juju Charms Collection) |
Invalid
|
Medium
|
Unassigned |
Bug Description
The odl-controller charm has its own settings for http and https proxy (and not a no-proxy one). It should use whatever juju is using, including no-proxy.
no longer affects: | landscape |
tags: | added: kanban-cross-team |
Changed in odl-controller (Juju Charms Collection): | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 16.01 |
Changed in odl-controller (Juju Charms Collection): | |
milestone: | 16.01 → 16.04 |
Changed in odl-controller (Juju Charms Collection): | |
milestone: | 16.04 → 16.07 |
Changed in odl-controller (Juju Charms Collection): | |
milestone: | 16.07 → 16.10 |
Changed in odl-controller (Juju Charms Collection): | |
milestone: | 16.10 → 17.01 |
Changed in charm-odl-controller: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in odl-controller (Juju Charms Collection): | |
status: | Triaged → Invalid |
To post a comment you must log in.
The proxy settings are used directly in the maven integration in ODL to point the module install process at a proxy; that said, I think it would make sense to have the charm observe juju provided settings if provided.