Usability: machine provisioning timeouts
Bug #1386222 reported by
James Page
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Wishlist
|
Unassigned | ||
| juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
Having some sort of timeout on machine provisioning might be nice; I've been working in a test environment where the hardware is not 100% reliable - figuring out what's missing and then doing a force-terminate and re-provision can be a little fiddly as environment typically have 500 units and >1500 agents running so juju status is quite busy.
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 1.21-alpha3 |
| tags: | added: deploy |
| Changed in juju-core: | |
| importance: | High → Medium |
| milestone: | 1.21-alpha3 → none |
| tags: |
added: scalability removed: scale-testing |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
Is this alpha2? We are tracking a some performance degradations on bootstrap and upgrade that might be in play here?