Public bug reported: Testing with 20100823 ISO, eucalyptus 2.0~bzr1233-0ubuntu1 Topology 1 (CLC+Walrus+CC+SC / NC)
/var/log/eucalyptus/registration.log shows that Walrus and CC fail to register (euca_conf returns 1); the SC loops waiting for the cluster to appear. Running manually, once booted: $ sudo -u eucalyptus /usr/share/eucalyptus/registration/walrus <ip> $ sudo -u eucalyptus /usr/share/eucalyptus/registration/cluster <clustername> <ip> works. The SC autoregisters correctly once the cluster registers. I suspect our current logic in upstart script makes it try to register too early. uec-component-listener starts when eucalyptus-cloud and eucalyptus-cc are started, and maybe it should wait a bit more. This is definitely a race, and the 5400rpm disks on the test laptop probably slows down the noisy component startup to a point where boot- time autoregistration fails. ** Affects: eucalyptus (Ubuntu) Importance: High Assignee: Dave Walker (davewalker) Status: New ** Affects: eucalyptus (Ubuntu Maverick) Importance: High Assignee: Dave Walker (davewalker) Status: New ** Changed in: eucalyptus (Ubuntu) Importance: Undecided => High ** Changed in: eucalyptus (Ubuntu) Milestone: None => ubuntu-10.10-beta ** Changed in: eucalyptus (Ubuntu) Assignee: (unassigned) => Dave Walker (davewalker) ** Also affects: eucalyptus (Ubuntu Maverick) Importance: High Assignee: Dave Walker (davewalker) Status: New -- [maverick] Autoregistration of components fails at boot time (euca_conf returns 1) https://bugs.launchpad.net/bugs/622698 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