DumpModels fails when new unit added
Bug #1742036 reported by
Stuart Bishop
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Using the Juju API, if I call DumpModels on a model that has just started instantiating a new unit, it fails with various error messages (depending on how far along the race condition gets):
agent binaries for unit "ubuntu/0" not found
missing instance data for machine 1 not valid
agent binaries for machine 1 not found
I'm using the Juju API to watch for changes, and using DumpModels to get snapshots of the models, so this happens pretty much every time
Revision history for this message
| Tim Penhey (thumper) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: developer-mode dump-model |
| tags: |
added: canonical-is removed: developer-mode dump-model |
| tags: | added: bitesize |
Revision history for this message
| Tim Penhey (thumper) wrote | #2 |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This is due to the export code also calling Validate.
I think we should allow dump-model to skip the validate.
Validate is used to ensure that the model is in a stable state for migration, which doesn't always make sense with this command.