Since Jaunty is EOL, closing Jaunty task as Won't Fix.
** Changed in: eucalyptus (Ubuntu Jaunty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/364723
Title:
euca
Per Etienne, marking fix released in Karmic.
I'll leave it open against Jaunty for now, in case an SRU is necessary,
though I'd expect this is probably a "won't fix", please upgrade to
Karmic situation.
:-Dustin
** Also affects: eucalyptus (Ubuntu Jaunty)
Importance: Undecided
Status:
This bug have been fixed in karmic. It should be SRUed for jaunty, or
marked WONTFIX, as appropriate.
--
eucalyptus-nc service fail to start at boot, cannot connect to libvirtd
https://bugs.launchpad.net/bugs/364723
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Nilesh, as of your second comment, you need to change the value of
VNET_BRIDGE in /etc/eucalyptus/eucalyptus.conf on the node controllers.
--
eucalyptus-nc service fail to start at boot, cannot connect to libvirtd
https://bugs.launchpad.net/bugs/364723
You received this bug notification because y
Changing the start order will have eucalyptus-nc start after a reboot:
$ sudo update-rc.d -f eucalyptus-nc remove
$ sudo update-rc.d eucalyptus-nc start 99 1 2 3 4 5 . stop 99 0 6 .
--
eucalyptus-nc service fail to start at boot, cannot connect to libvirtd
https://bugs.launchpad.net/bugs/364723
Then I restart as below.
nil...@asterisk:~$ sudo /etc/init.d/eucalyptus-nc restart
* Restarting Eucalyptus Node Controller
Warning! Cannot find bridge xenbr0: instances may be without net
And look at the log again which show no issues this time.
nil...@asterisk:~$ cat /var/log/eucalyptus/euca
at boot, jaunty server shows
Node Controller cannot be started: errors in
/var/log/eucalytpus/euca_test_nc.log
my copy of /var/log/eucalytpus/euca_test_nc.log is below:
nil...@asterisk:~$ cat /var/log/eucalyptus/euca_test_nc.log
This is perl, v5.10.0 built for x86_64-linux-gnu-thread-multi
Cop
Yes indeed, /etc/init.d/eucalyptus-nc (re)start once the node controller
is done booting work as expected.
--
eucalyptus-nc service fail to start at boot, cannot connect to libvirtd
https://bugs.launchpad.net/bugs/364723
You received this bug notification because you are a member of Ubuntu
Bugs,
I presume restarting the node controller fixes it?
Starting eucalyptus at S20 is too early anyway. It really should be
around S90 or something.
--
eucalyptus-nc service fail to start at boot, cannot connect to libvirtd
https://bugs.launchpad.net/bugs/364723
You received this bug notification bec
