Impossible to cancel bootstrap
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju |
High
|
Ben Hoyt | ||
| | 2.9 |
High
|
Ben Hoyt | ||
| | 3.0 |
High
|
Ben Hoyt | ||
Bug Description
Bootstrapping was taking too long (10min+), so I tried to cancel it. It doens't work.
Host is bionic, juju snap is:
juju 2.6.6 8594 stable canonical✓ classic
lxd works just fine on this host.
$ juju bootstrap lxd --keep-broken
Creating Juju controller "localhost-
Looking for packaged Juju agent version 2.6.6 for amd64
To configure your system to better support LXD containers, please see: https:/
Launching controller instance(s) on localhost/
- juju-a83592-0 (arch=amd64)
Installing Juju agent on bootstrap instance
Fetching Juju GUI 2.14.0
Waiting for address
Attempting to connect to 10.0.100.216:22
Connected to 10.0.100.216
Running machine configuration script...
^CInterrupt signalled: waiting for bootstrap to exit
Bootstrap agent now started
Contacting Juju controller at 10.0.100.216 to verify accessibility...
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
^CInterrupt signalled: waiting for bootstrap to exit
| Tim Penhey (thumper) wrote : | #2 |
While this may be intentional, it isn't good user experience.
We should be able to determine that there is a machine deployed by the cloud provider, and kill that.
| Changed in juju: | |
| status: | Invalid → Triaged |
| importance: | Undecided → Medium |
| Heather Lanigan (hmlanigan) wrote : | #3 |
We now have at least 4 duplicates of this bug. Any issues making a high priority?
| Changed in juju: | |
| importance: | Medium → High |
| Ben Hoyt (benhoyt) wrote : | #4 |
This is addressed in https:/
It's not perfect, as the code only checks for cancellation after various points (rather than wiring context.Context through to the "bottom" layers, as that would require a lot more churn). And of course you still have to wait for teardown. For LXD this is quite quick -- just a few seconds -- but for cloud providers like AWS teardown can take a minute or two. If you press Ctrl-C again during teardown, the Juju client says "Ctrl-C pressed, cleaning up failed bootstrap".
| Changed in juju: | |
| assignee: | nobody → Ben Hoyt (benhoyt) |
| milestone: | none → 2.8.8 |
| status: | Triaged → Fix Committed |
| Ben Hoyt (benhoyt) wrote : | #5 |
PR to merge fix into 2.9 and develop:
* 2.9: https:/
* develop: https:/
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
This is intentional.
Aborting immediately will leave things running on the host. To get out of this straight away, use Ctrl+Z to kill the process, then run `juju kill-controller`.