tabular format does not give enough details about machine provisioning errors
Bug #1478156 reported by
Marco Ceppi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Eric Snow | ||
| 1.25 |
Fix Released
|
High
|
Eric Snow | ||
Bug Description
Since tabular format is going to be default it needs to elevate machine provisioning errors. When running `juju status --format=tabular` or using the Juju flag for status 2.0, when a machine fails to provision this is what's provided (see machine 5)
http://
When --format yaml is used, the user will actually see the error
http://
It seems agent-state-info is the key, but it should be easy to determine that when an a provisioning error is made the STATE field (empty atm) could have an "error" or "provisioning error" if error is already used. As to the untrained eye it seems like GCE is just taking a long ass time to create the instance since inst-id is pending.
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 1.25.0 |
| summary: |
- summary format does not give enough details about machine provisioning + tabular format does not give enough details about machine provisioning errors |
| Changed in juju-core: | |
| milestone: | 1.25-alpha1 → 1.25-beta1 |
| Changed in juju-core: | |
| milestone: | 1.25-beta1 → 1.25.1 |
| Changed in juju-core: | |
| assignee: | nobody → Eric Snow (ericsnowcurrently) |
| status: | Triaged → In Progress |
| milestone: | 1.25.1 → 1.26.0 |
| milestone: | 1.26.0 → none |
Revision history for this message
| Eric Snow (ericsnowcurrently) wrote | #1 |
Revision history for this message
| Eric Snow (ericsnowcurrently) wrote | #2 |
Revision history for this message
| Eric Snow (ericsnowcurrently) wrote | #3 |
Revision history for this message
| Eric Snow (ericsnowcurrently) wrote | #4 |
Revision history for this message
| Eric Snow (ericsnowcurrently) wrote | #5 |
Revision history for this message
| Eric Snow (ericsnowcurrently) wrote | #6 |
Revision history for this message
| Eric Snow (ericsnowcurrently) wrote | #7 |
| Changed in juju-core: | |
| milestone: | none → 1.26-alpha1 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
From what I can tell, the message in "agent-state-info" indicates that provisioning failed. If that were the case then AgentState should have been set to "error". [1] Instead it appears to be unset. This implies to me that there is a bug in how instance provisioning failures are handled. I'm going to look into that here. If it turns out I've misunderstood then I'll circle back to injecting a more meaningful message in this case.
[1] https:/