Ephemeral environment during curtin installation doesn't use proxy
Bug #1496961 reported by
Andres Rodriguez
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Blake Rouse | ||
Bug Description
Trying to install a machine with mlaltest trunk, I came itno an issue where:
When deploying, the ephemeral environment tries to access the archive, however, it does it without going to the proxy first, and tries to do it directly.
However, when curtin takes over and installs packages, these are installed using the proxy.
This means that either
1. proxy is not set for the pehemeral environment
2. proxy is set only after curtin takes over
Or some other reason.
Related branches
lp:~blake-rouse/maas/cloud-init-apt-proxy
- Blake Rouse (community): Approve
-
Diff: 199 lines (+47/-25)4 files modifiedetc/maas/templates/commissioning-user-data/user_data_config.template (+0/-6)
src/maasserver/compose_preseed.py (+34/-15)
src/maasserver/preseed.py (+1/-1)
src/maasserver/tests/test_compose_preseed.py (+12/-3)
| Changed in maas: | |
| milestone: | none → 1.9.0 |
| importance: | Undecided → High |
| status: | New → Confirmed |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #1 |
Download full text (3.5 KiB)
| Changed in maas: | |
| status: | Confirmed → Triaged |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #2 |
| Changed in curtin: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| Changed in maas: | |
| importance: | High → Critical |
| tags: | added: ci |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #3 |
| Changed in curtin: | |
| status: | Triaged → Invalid |
| Changed in maas: | |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| no longer affects: | curtin |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is breaking the MAAS CI at the moment as well. The CI does all network communication through the proxy. Here is the installation log:
Err http://
Err http://
Err http://
Err http://
Unable to connect to archive.
Err http://
Unable to connect to security.
Err http://
Unable to connect to archive.
Reading package lists...
W: Failed to fetch http://
W: Failed to fetch http://
W: Failed to fetch http://
W: Failed to fetch http://
W: Failed to fetch http://
W: Failed to fetch http://
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package bcache-tools
Unexpected error while running command.
Command: ['eatmydata', 'apt-get', 'install', '--quiet', '--assume-yes', '--option=
Exit code: 100
Reason: -
Stdout: ''
Stderr: ''
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: "Err http://