Public bug reported:
Testing 20091005 daily CD, UEC/Cluster install
After the install reboot, eucalyptus doesn't autoregister. The registration
logs all contain:
ERROR: you need to be on the CLC host and the CLC needs to be running.
Restarting eucalyptus, or upgrading to a new eucalyptus package,
autoregistration works correctly.
The only failure scenario seems to be when the first time the service is
started also happens to be at system startup time.
I am wondering if we don't start eucalyptus at boot a little too early with:
start on runlevel [23]
Maybe the network and/or eth0 is not fully operational at that point,
resulting in wrong addresses being used in /etc/eucalyptus/eucalyptus-
ipaddr.conf. That might also explain the strange walrus 127.0.0.1
registration I experienced last week.
** Affects: eucalyptus (Ubuntu)
Importance: High
Status: Triaged
** Affects: eucalyptus (Ubuntu Karmic)
Importance: High
Status: Triaged
** Changed in: eucalyptus (Ubuntu)
Status: New => Triaged
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => High
** Also affects: eucalyptus (Ubuntu Karmic)
Importance: High
Status: Triaged
--
No autoregistration on first startup after ISO install
https://bugs.launchpad.net/bugs/443118
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
