Wget on Designate-Bind fails with proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Designate-Bind Charm |
Fix Released
|
Low
|
Drew Freiberger |
Bug Description
Designate-Bind executes a wget during zone syncing among multiple peers.
The function can be found on: https:/
The issue is that wget may not work on an environment with a proxy. To make it work, it is needed to set http_proxy/no_proxy variables besides juju_http_
Once http_proxy is defined, it means that applications system-wide will hit the same proxy, which is not necessarily what we want (we might want to define, for example, juju to hit one proxy and wgets or snaps hitting addresses/urls directly or via second proxy). For that, we need to find the right combination for http_proxy/no_proxy + juju_http_
We need that sync step to be redesigned and it to rely on Juju's env variables.
tags: | added: cpe-onsite |
Changed in charm-designate-bind: | |
milestone: | none → 19.04 |
Changed in charm-designate-bind: | |
assignee: | nobody → Drew Freiberger (afreiberger) |
As the sync is always sourced from the lead unit, it would make sense to unset and proxy configuration during this call.