After enable-ha, machine failed to provision and now juju is completely stuck
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Unassigned | ||
Bug Description
dpb@helo:slaves[0]$ juju status
Model Controller Cloud/Region Version
controller lrc-region1 lrc/region1 2.0.2.1
App Version Status Scale Charm Store Rev OS Notes
Unit Workload Agent Machine Public address Ports Message
Machine State DNS Inst id Series AZ
0 started 10.96.127.14 4cada057-
1 pending 10.96.127.25 110a1297-
2 pending 10.96.127.13 655bcbdf-
3 down pending xenial
4 down pending xenial
5 down pending xenial
6 down pending xenial
dpb@helo:slaves[0]$ juju remove-machine --force 1 2 3 4 5 6
ERROR no machines were destroyed: machine is required by the model; machine is required by the model; machine is required by the model; machine is required by the model; machine is required by the model; machine is required by the model
I ran into a bug in deploying machine 1 and 2 with a enable-ha -n 3 call. Now, I cannot back out of this situation. machine 1 and 2 are not going to come up, and are not recoverable. Juju is also failing to provision *any* new machines on *any* model.
all new machines look like machines 3-6 'down' state, 'pending' instance-id.
This bug is particularly bad since the whole controller is now wedged.
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.1.0 |
| Felipe Reyes (freyes) wrote | #1 |
For the records, this issue has been raised in the past https:/