The node controller sometimes fails to start if libvirt is not ready
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Medium
|
Dustin Kirkland | ||
libvirt (Ubuntu) |
Fix Released
|
Medium
|
Dustin Kirkland |
Bug Description
While rebooting node controllers multiple times, the nc fails sometimes to start. It seems related to libvirt not being ready as noted in /var/log/
ubuntu@uec-nc4:~$ cat /var/log/
This is perl, v5.10.0 built for x86_64-
Copyright 1987-2007, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://
total_memory=891
nr_cores=2
libvir: Remote error : unable to connect to '/var/run/
libvirt error: unable to connect to '/var/run/
error: failed to connect to hypervisor
ubuntu@uec-nc4:~$
Restarting eucalyptus-nc fixes the problem: the ressource of the node are correctly registered with the CC.
Changed in eucalyptus (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in eucalyptus (Ubuntu): | |
importance: | Medium → Low |
Changed in eucalyptus (Ubuntu): | |
status: | Triaged → In Progress |
Ideally, we'd have an upstart libvirt configuration, and we'd solve Bug #438631.
Then, we could ensure that the necessary resources are available.
:-Dustin