swift-storage should always assume noproxy for swift-proxy's IP
Bug #1401666 reported by
Ante Karamatić
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Swift Storage Charm |
Triaged
|
Medium
|
Unassigned | ||
| swift-storage (Juju Charms Collection) |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
In an environment where proxy for http exists, adding relation between swift-storage (SS) and swift-proxy (SP) will fail.
What happens is that juju provides http_proxy and no-proxy options to SS, which then uses that when it wgets rings from SP. Since SP's IP is not in no-proxy variable, wget might fail, depending on http proxy's configuration (it could be set to proxy only external requests). This can be fixed by adding SP's IP into juju's no-proxy variable. But, the problem is that IP might be unknown until SP is deployed. This is easy to solve when VIP for SP is known before deploying.
Ideally, SS would always append SP's VIP and SP's IP to no-proxy provided by juju.
| tags: | added: cts |
| description: | updated |
Revision history for this message
| James Page (james-page) wrote | #1 |
Revision history for this message
| James Page (james-page) wrote | #2 |
| Changed in swift-storage (Juju Charms Collection): | |
| importance: | Undecided → Medium |
| status: | New → Opinion |
| status: | Opinion → Triaged |
Revision history for this message
| James Page (james-page) wrote | #3 |
| Changed in charm-swift-storage: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in swift-storage (Juju Charms Collection): | |
| status: | Triaged → Invalid |
To post a comment you must log in.
Ideally we'd not proxy traffic for any IP that resides within the deployment but I think that's beyond the scope of what we should be doing in the charm.