Ubuntu
eucalyptus package

Duplicate registration tries show up in registration.log

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

Bug Description

20100831/Maverick beta candidate, Topology 1, amd64 and i386

The registration.log shows that uec-component-listener receives two announces for each component and tries to process the two of them. The first one succeeds, the other one fails.

2010-09-01 10:44:37+02:00 | 3866 -> Calling storage cluster1 storage 192.168.0.33
2010-09-01 10:44:37+02:00 | 3864 -> Calling cluster cluster1 192.168.0.33
2010-09-01 10:44:37+02:00 | 3862 -> Calling walrus Walrus 192.168.0.33
2010-09-01 10:44:37+02:00 | 3865 -> Calling walrus Walrus 192.168.0.33
2010-09-01 10:44:37+02:00 | 3863 -> Calling storage cluster1 storage 192.168.0.33
2010-09-01 10:44:37+02:00 | 3867 -> Calling cluster cluster1 192.168.0.33
2010-09-01 10:44:39+02:00 | 3863 -> Cluster cluster1 doesn't exist, retrying in 10 seconds.
2010-09-01 10:44:39+02:00 | 3866 -> Cluster cluster1 doesn't exist, retrying in 10 seconds.
2010-09-01 10:44:39+02:00 | 3865 -> euca_conf --register-walrus returned FAILURE (error 1): Command attempted was "/usr/sbin/euca_conf --no-rsync --skip-scp-hostcheck --register-walrus 192.168.0.33", and had the following output: "Adding WALRUS host 192.168.0.33
ERROR: failed to register Walrus, please log in to the admin interface and check cloud status."
2010-09-01 10:44:41+02:00 | 3867 -> euca_conf --register-cluster returned FAILURE (error 1): Command attempted was "/usr/sbin/euca_conf --no-rsync --skip-scp-hostcheck --register-cluster cluster1 192.168.0.33", and had the following output: "ERROR: failed to register new cluster, please log in to the admin interface and check cloud status."
2010-09-01 10:44:41+02:00 | 3864 -> euca_conf --register-cluster returned SUCCESS
2010-09-01 10:44:42+02:00 | 3862 -> euca_conf --register-walrus returned SUCCESS
2010-09-01 10:44:50+02:00 | 3866 -> euca_conf --register-sc returned FAILURE (error 1): Command attempted was "/usr/sbin/euca_conf --no-rsync --skip-scp-hostcheck --register-sc cluster1 192.168.0.33", and had the following output: "Adding SC 192.168.0.33 to cluster cluster1
ERROR: failed to register storage controller, please log in to the admin interface and check cloud status."
2010-09-01 10:44:50+02:00 | 3863 -> euca_conf --register-sc returned SUCCESS

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

Note that everything is working properly, despite the failures in the log. This doesn't prevent the components to register correctly.

Changed in eucalyptus (Ubuntu):
importance: Undecided → Low
Revision history for this message
Dave Walker (davewalker) wrote :

I was able to reproduce this.

Changed in eucalyptus (Ubuntu):
status: New → Confirmed
Ubuntu QA Website (ubuntuqa)
tags: added: iso-testing
Thierry Carrez (ttx)
tags: added: server-mrs
Revision history for this message
Dave Walker (davewalker) wrote :

I am pretty sure this is an event for both IPv4 and IPv6. Whilst IPv6 isn't supported by euca_conf, it surely will soon. Is this really a defect?

Changed in eucalyptus (Ubuntu Maverick):
status: Confirmed → Incomplete
Revision history for this message
Thierry Carrez (ttx) wrote :

Right, it's probably two announcements, one for IPv4 and one for IPv6, the two of them using the same mechanics to determine the "one and only IPv4 address" and pass it as a parameter on the announce.

It's not a problem if registration is atomic and idempotent...

Changed in eucalyptus (Ubuntu Maverick):
status: Incomplete → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 2.0+bzr1241-0ubuntu2

---------------
eucalyptus (2.0+bzr1241-0ubuntu2) maverick; urgency=low

  * debian/registration/uec_component_listener.c: Ignore IPv6 avahi broadcasts.
    Both IPv4 and IPv6 broadcasts are dispatched from the components. A
    registration attempt was therefore made for each. As IPv6 isn't supported
    the processing when caught is now ignored. (LP: #627963, #628025)
 -- Dave Walker (Daviey) <email address hidden> Mon, 20 Sep 2010 16:57:24 +0100

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

Other bug subscribers

Remote bug watches

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