Machine agent randomly uninstalled itself
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Achilleas Anagnostopoulos | ||
2.5 |
Fix Released
|
Critical
|
Achilleas Anagnostopoulos | ||
2.6 |
Fix Released
|
Critical
|
Achilleas Anagnostopoulos |
Bug Description
This is in a Juju 2.4.7 environment using AWS.
I noticed of our machines was "down" in Juju status, with failed unit hooks also visible.
SSH'd to the unit to see what was up, and found that the jujud-machine-3 systemd service files no longer exist, and that /var/lib/juju/tools has also gone, likely among others.
The only unusual lines in jujud-machine-3.log are right at the end, with no apparent cause:
2019-04-27 05:47:15 INFO juju.agent uninstall.go:36 marking agent ready for uninstall
2019-04-27 05:47:15 INFO juju.worker.
2019-04-27 05:47:15 INFO juju.agent uninstall.go:47 agent already marked ready for uninstall
2019-04-27 05:47:15 INFO juju.cmd.jujud machine.go:1238 uninstalling agent
2019-04-27 05:47:16 INFO cmd supercommand.go:465 command finished
Changed in juju: | |
milestone: | 2.6.1 → 2.6.2 |
Changed in juju: | |
milestone: | 2.6.2 → 2.6.3 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | Fix Committed → Fix Released |
I've now come across this in another two units in a separate (Juju 2.5.1 on GCE) environment also, so this isn't AWS specific, nor is it 2.4 specific.