Merge lp:~axwalk/juju-core/lp1238948-sigabrt-uninstall into lp:~go-bot/juju-core/trunk
Status: | Merged |
---|---|
Approved by: | Andrew Wilkins |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2188 |
Proposed branch: | lp:~axwalk/juju-core/lp1238948-sigabrt-uninstall |
Merge into: | lp:~go-bot/juju-core/trunk |
Diff against target: |
246 lines (+175/-2) 5 files modified
cmd/jujud/machine.go (+4/-0) provider/null/environ.go (+23/-1) provider/null/environ_test.go (+29/-1) worker/terminationworker/worker.go (+60/-0) worker/terminationworker/worker_test.go (+59/-0) |
To merge this branch: | bzr merge lp:~axwalk/juju-core/lp1238948-sigabrt-uninstall |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email: mp+200767@code.launchpad.net |
Commit message
provider/null: implement Environ.Destroy
A new worker is introduced: worker/
This worker simply waits for a signal (SIGABRT), and
then exits with ErrTerminateAgent. This causes the
agent to uninstall itself. We do not use SIGTERM, as
that would cause "service stop jujud-machine-N" to
uninstall the agent.
The null/manual provider has been updated at the same
time to implement Environ.Destroy. The Destroy method
simply connects to the bootstrap machine via SSH, and
issues "sudo pkill -SIGABRT jujud". We only do this
for machine 0, as Destroy will never be reached until
all non-manager machines are destroyed.
Fixes #1238948
Description of the change
provider/null: implement Environ.Destroy
A new worker is introduced: worker/
This worker simply waits for a signal (SIGABRT), and
then exits with ErrTerminateAgent. This causes the
agent to uninstall itself. We do not use SIGTERM, as
that would cause "service stop jujud-machine-N" to
uninstall the agent.
The null/manual provider has been updated at the same
time to implement Environ.Destroy. The Destroy method
simply connects to the bootstrap machine via SSH, and
issues "sudo pkill -SIGABRT jujud". We only do this
for machine 0, as Destroy will never be reached until
all non-manager machines are destroyed.
Fixes #1238948
Reviewers: mp+200767_ code.launchpad. net,
Message:
Please take a look.
Description:
provider/null: implement Environ.Destroy
A new worker is introduced: worker/ terminationwork er.
This worker simply waits for a signal (SIGABRT), and
then exits with ErrTerminateAgent. This causes the
agent to uninstall itself. We do not use SIGTERM, as
that would cause "service stop jujud-machine-N" to
uninstall the agent.
The null/manual provider has been updated at the same
time to implement Environ.Destroy. The Destroy method
simply connects to the bootstrap machine via SSH, and
issues "sudo pkill -SIGABRT jujud". We only do this
for machine 0, as Destroy will never be reached until
all non-manager machines are destroyed.
Fixes #1238948
https:/ /code.launchpad .net/~axwalk/ juju-core/ lp1238948- sigabrt- uninstall/ +merge/ 200767
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/48950043/
Affected files (+177, -2 lines): machine. go null/environ. go null/environ_ test.go terminationwork er/worker. go terminationwork er/worker_ test.go
A [revision details]
M cmd/jujud/
M provider/
M provider/
A worker/
A worker/