Complain loudly and clearly on the console when cloud-init fails to run
Bug #1621082 reported by
Christian Reis
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
When cloud-init itself fails to run, as in the case discussed in bug 1621075, an experienced user can detect the problem in the split-second the console is still alive, but most users are lost.
Could we make it more obvious what the problem we encountered was? I'm thinking of a very common problem in MAAS, which is that the initial network configuration is wrong, or drivers are not available for the NICs in the host.
| Changed in cloud-init: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
Revision history for this message
| James Falcon (falcojr) wrote | #1 |
| Changed in cloud-init: | |
| status: | Triaged → Won't Fix |
Revision history for this message
| James Falcon (falcojr) wrote | #2 |
To post a comment you must log in.
Running "cloud-init status" is the recommended way to obtain cloud-init status.