LXD REST API connection goes via proxy

Bug #2007297 reported by Adam Collard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Medium
Adam Collard
3.2
In Progress
High
Mauricio Faria de Oliveira
3.3
Fix Committed
High
Björn Tillenius

Bug Description

When MAAS talks to LXD it does so over a HTTP(S) connection using pylxd.

pylxd in turn uses requests to talk HTTP, which will respect os.environ["http_proxy"] and os.environ["https_proxy"] accordingly. If there are scenarios where those environment variables are set for the process that executes the pylxd commands, it will cause MAAS to try and reach the LXD endpoint via the provided proxy/ies.

This can be seen e.g. in systemtests

- Marking node failed: Power on for the node failed: Failed talking to node's BMC: Pod mg8atc: Failed to connect to the LXD REST API: HTTPSConnectionPool(host='1.1.1.1', port=8443): Max retries exceeded with url: /1.0?project=default (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden')))

Related branches

Changed in maas:
status: New → In Progress
assignee: nobody → Adam Collard (adam-collard)
importance: Undecided → Medium
milestone: none → 3.4.0
Changed in maas:
status: In Progress → Fix Committed
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.0-beta1
Alberto Donato (ack)
Changed in maas:
status: Fix Committed → Fix Released
Revision history for this message
Björn Tillenius (bjornt) wrote :

I'm marking this as High for 3.3, since it causes test failures for SolQA

Revision history for this message
Mauricio Faria de Oliveira (mfo) wrote :

Likewise for 3.2. Thanks, Björn!

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.