It is upstream bug https://bugs.launchpad.net/eucalyptus/+bug/517340
No, IMHO they shouldn't "fix" it at the init script level but in the
code itself.
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/512887
You received this bug notification because you are a member o
Hmm, you can report it upstream, if you like. Upstream uses sysvinit
scripts rather than upstart, so the issue may or may not be present
there, I'm not entirely sure...
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/512887
You received this bug notification because y
Great, thanks!
BTW, shouldn't this issue be reported upstream, to fix the NC to not loose the
socket?
Fixing eucalyptus-nc.upstart will handle the case of a "civilized" restart by
the sysadmin, but not if for instance the libvirtd dies and gets started by
hand with /usr/sbin/libvirtd -d right?
This bug was fixed in the package eucalyptus - 1.6.2~bzr1166-0ubuntu3
---
eucalyptus (1.6.2~bzr1166-0ubuntu3) lucid; urgency=low
* debian/eucalyptus-nc.upstart: handle libvirt restarts, LP: #512887
* eucalyptus-cc.eucalyptus-cc-publication.upstart,
eucalyptus-cloud.eucalyptus-
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/512887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
** Changed in: eucalyptus (Ubuntu Lucid)
Status: In Progress => Fix Committed
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/512887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Nevermind, Dan, I'm on it...
** Changed in: eucalyptus (Ubuntu Lucid)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Confirmed => In Progress
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/512887
You
Dan, looking for some advice here...
eucalyptus-nc definitely is not surviving libvirt-bin restarts. It
loses the socket. Is there an obvious way we can get eucalyptus-nc to
re-attach the socket on a libvirt restart?
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/5
Still a problem in current Lucid.
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/512887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: Medium
Status: Confirmed
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/512887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
We should test and confirm/fix and close this next week at the sprint.
** Changed in: eucalyptus (Ubuntu)
Milestone: None => lucid-alpha-3
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/512887
You received this bug notification because you are a member of Ubuntu
Needs reproduction on lucid / 1.6.2
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => Medium
** Changed in: eucalyptus (Ubuntu)
Status: New => Confirmed
--
Restarting libvirtd breaks Eucalyptus NC
https://bugs.launchpad.net/bugs/512887
You received this bug notification beca
12 matches
Mail list logo
