environs/openstack: juju status during large deployment fails
Bug #1169799 reported by
Dave Cheney
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Martin Packman | ||
Bug Description
Running juju status while doing a juju deploy -n200 runs the risk of a race as the machine may not have an instance id recorded.
machines:
status-error: instance 1510301 for machine 85 not found
services:
hadoop-master:
charm: cs:precise/hadoop-5
exposed: true
relations:
jobtracker:
- hadoop-slave
namenode:
- hadoop-slave
| Changed in juju-core: | |
| status: | Confirmed → Triaged |
| tags: | added: deploy race-condition status |
Revision history for this message
| William Reade (fwereade) wrote | #1 |
| Changed in juju-core: | |
| assignee: | nobody → Martin Packman (gz) |
| Changed in juju-core: | |
| status: | Triaged → Fix Released |
| Changed in juju-core: | |
| milestone: | 2.0 → none |
To post a comment you must log in.
Martin, I think your status work should have resolved this. Concur?