No autoregistration on first startup after ISO install

Bug #443118 reported by Thierry Carrez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
High
Unassigned
Karmic
Fix Released
High
Unassigned

Bug Description

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.

Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
Thierry Carrez (ttx) wrote :

I fail to reproduce the same error on subsequent boots (purging packages, diverting start/restart, reinstall, putting start/restart back and reboot). Might be some first-boot DHCP query racing eucalyptus.

Revision history for this message
Thierry Carrez (ttx) wrote :

Could not reproduce on my 20091006 CD test.
Note that I had the following message in walrus registration logs:

::::::::::::::
/var/log/eucalyptus/walrus-registration.log
::::::::::::::
Adding WALRUS host 192.168.0.127
Walrus is not up on host 192.168.0.127: check the logs

SUCCESS: new walrus on host '192.168.0.127' successfully registered.

Closing as Fix released, anyone please reopen if you have autoregistration issues on >=20091006 CD installs.

Changed in eucalyptus (Ubuntu Karmic):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.