Juju Zookeeper node agent does not handle reboots

Bug #987853 reported by Dafang Zhang
20
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

[1] https://bugs.launchpad.net/juju/+bug/863526

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Just had the same thing happen, and restarting the agent did fix the issue. Marking Confirmed/High.

juju:
  Installed: 0.5+bzr531-1juju5~precise1
  Candidate: 0.5+bzr531-1juju5~precise1
  Version table:
 *** 0.5+bzr531-1juju5~precise1 0
        500 http://ppa.launchpad.net/juju/pkgs/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status
     0.5+bzr531-0ubuntu1 0
        500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

Changed in juju:
status: New → Confirmed
importance: Undecided → High
milestone: none → galapagos
Changed in juju:
milestone: galapagos → honolulu
Changed in juju:
milestone: 0.6 → none
Martin Packman (gz)
Changed in juju-core:
importance: Undecided → High
Revision history for this message
Dave Cheney (dave-cheney) wrote :

I believe that we have resolved this issue in juju-core. I will test this for the 1.9.4 release.

Changed in juju-core:
assignee: nobody → Dave Cheney (dave-cheney)
no longer affects: juju-core
Changed in juju:
milestone: none → 0.8
Curtis Hovey (sinzui)
Changed in juju:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.