manual provider fails to remove itself if bootstrapping fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
The manual provider was unable to setup the machine correctly, something went wrong with mongodb so the jujud agent will eventually time out.
The manual provider failed to remove /etc/init/
2014-03-24 01:02:01 ERROR juju.environs.
2014-03-24 01:02:01 DEBUG juju.utils.ssh ssh.go:226 using OpenSSH ssh client
2014-03-24 01:02:01 DEBUG juju.utils.ssh ssh_openssh.go:147 running: ssh -o "StrictHostKeyC
2014-03-24 01:02:06 ERROR juju.cmd.juju common.go:19 Bootstrap failed, and the environment could not be destroyed: rc: 1
2014-03-24 01:02:06 ERROR juju.cmd supercommand.go:296 rc: 1
Related branches
- Juju Engineering: Pending requested
-
Diff: 73 lines (+30/-4)2 files modifiedprovider/manual/environ.go (+19/-2)
provider/manual/environ_test.go (+11/-2)
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
milestone: | 1.18.0 → 1.17.7 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Yep, the manual provider expects there to be a machine agent to take care of the environment destruction. We should (a) permit pkill to fail with rc 1, and have fallback code like in the local provider to handle failed bootstrap.