maas: deploying waiter fails and exits 1
Bug #2073402 reported by
Guillaume Boutry
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Snap |
Triaged
|
Critical
|
Unassigned | ||
Bug Description
The connection to the controller can be lost while waiting for the machines to be deployed (see logs attached)
Waiting for machines to be deployed and then re-running the deploy command will resume the deployment.
Revision history for this message
| Guillaume Boutry (gboutry) wrote | #1 |
| summary: |
- maas: deploying waiter fails and stop dp + maas: deploying waiter fails and exits 1 |
| tags: | added: pc |
Revision history for this message
| Guillaume Boutry (gboutry) wrote | #2 |
| Changed in snap-openstack: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| tags: | added: open-2271 |
To post a comment you must log in.
If the sunbeam command is re-run too fast, it will not recognized the current deploying machine and will try to allocate new ones.
The deployment ended up with 14 machines defined in Juju.
If the sunbeam command is re-run after the machines are marked as deployed in Juju/MAAS, then sunbeam will correctly consider the machines, and no new machines will be deployed.