Juju Zookeeper node agent does not handle reboots
Bug #987853 reported by
Dafang Zhang
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
High
|
Unassigned |
Bug Description
The issue addressed in Bug #863526 [1] has been resolved for juju service node, but the Zookeeper node still does not handle reboot. However, the workaround described in the comments area for Bug #863526 seemed still to work fine for the Zookeeper node after rebooting.
restart juju-machine-agent
Changed in juju: | |
milestone: | galapagos → honolulu |
Changed in juju: | |
milestone: | 0.6 → none |
Changed in juju-core: | |
importance: | Undecided → High |
no longer affects: | juju-core |
Changed in juju: | |
milestone: | none → 0.8 |
Changed in juju: | |
status: | Confirmed → Triaged |
To post a comment you must log in.
Just had the same thing happen, and restarting the agent did fix the issue. Marking Confirmed/High.
juju: 1juju5~ precise1 1juju5~ precise1 1juju5~ precise1 0 ppa.launchpad. net/juju/ pkgs/ubuntu/ precise/main amd64 Packages dpkg/status 5+bzr531- 0ubuntu1 0 us-east- 1.ec2.archive. ubuntu. com/ubuntu/ precise/universe amd64 Packages
Installed: 0.5+bzr531-
Candidate: 0.5+bzr531-
Version table:
*** 0.5+bzr531-
500 http://
100 /var/lib/
0.
500 http://