[2.2] MAAS doesn't report cloud-init failures post-deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Andres Rodriguez |
Bug Description
A node has been marked as "Deployed" in MAAS, but it actually failed.
1. Deploy -> curtin succeeded with no error
2. Reboot at the end of curtin process
3. Boot up with installed OS, then cloud-init will be run
At the moment, MAAS marked the node as Deployed, but cloud-init is still running and it has some failures (in my case, failure in cloudinit.
Cloud-init output of phase 3. above:
[ 26.808179] cloud-init[4574]: 2017-08-01 06:56:06,869 - util.py[WARNING]: Running module apt-configure (<module 'cloudinit.
[ 49.828301] cloud-init[4574]: Ign:1 http://
[ 49.828437] cloud-init[4574]: Ign:2 http://
[ 49.828522] cloud-init[4574]: Ign:3 http://
[ 49.828605] cloud-init[4574]: Ign:4 http://
[ 49.829045] cloud-init[4574]: Ign:5 http://
[ 49.829565] cloud-init[4574]: Ign:6 http://
[ 49.829922] cloud-init[4574]: Ign:7 http://
[ 49.830477] cloud-init[4574]: Ign:8 http://
...
[ 52.823275] cloud-init[4574]: Reading package lists...
[ 52.823343] cloud-init[4574]: W: The repository 'http://
[ 52.823412] cloud-init[4574]: W: The repository 'http://
[ 52.823481] cloud-init[4574]: W: The repository 'http://
[ 53.194853] cloud-init[4574]: W: The repository 'http://
[ 53.194961] cloud-init[4574]: E: Failed to fetch http://
[ 53.195039] cloud-init[4574]: E: Failed to fetch http://
[ 53.195113] cloud-init[4574]: E: Failed to fetch http://
[ 53.195185] cloud-init[4574]: E: Failed to fetch http://
[ 53.195272] cloud-init[4574]: E: Some index files failed to download. They have been ignored, or old ones used instead.
[ 70.444562] cloud-init[4574]: 2017-08-01 06:56:50,523 - handlers.
Thus, no ntp setup with MAAS as a result.
Related branches
- Mike Pontillo (community): Approve
-
Diff: 58 lines (+10/-1)3 files modifiedsrc/metadataserver/api.py (+2/-0)
src/metadataserver/tests/test_api.py (+3/-1)
src/provisioningserver/events.py (+5/-0)
summary: |
- MAAS should not mark a node as "Deployed" when cloud-init has some + [2.2] MAAS should not mark a node as "Deployed" when cloud-init has some failures |
Changed in maas: | |
status: | Won't Fix → Incomplete |
Changed in maas: | |
assignee: | nobody → Andres Rodriguez (andreserl) |
summary: |
- [2.2] MAAS should not mark a node as "Deployed" when cloud-init has some - failures + [2.2] MAAS doesn't report cloud-init failures post-deployment |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.0alpha3 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
The machine is marked deployed once it access the metadata which ensures the SSH key gets imported. If other cloud-init failures happen, like yours, it is ok because as you said, it could have been just random issues that happen.