[Bug 446036] [NEW] The node controller sometimes fails to start if libvirt is not ready

[Mathias Gug]

Public bug reported:

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/eucalyptus/euca_test_nc.log:

ubuntu at uec-nc4:~$ cat /var/log/eucalyptus/euca_test_nc.log

This is perl, v5.10.0 built for x86_64-linux-gnu-thread-multi

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://www.perl.org/, the Perl Home Page.

total_memory=891
nr_cores=2
libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory
libvirt error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory (code=38)
error: failed to connect to hypervisor
ubuntu at uec-nc4:~$

Restarting eucalyptus-nc fixes the problem: the ressource of the node
are correctly registered with the CC.

** Affects: eucalyptus (Ubuntu)
     Importance: Undecided
         Status: New

-- 
The node controller sometimes fails to start if libvirt is not ready
https://bugs.launchpad.net/bugs/446036
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.