Comment 27 for bug 627963

Got the problem as described above on a Intel Xeon. Did the workaround #9 and --register-cluster without stop/start eucalyptus!

Using eucalyptus (2.0+bzr1241-0ubuntu4.1) on Maverick Meerkat (10.10).

After the reboot, again --deregister-cluster and then --register-cluster. No error's!

But it is reproducible when:

sudo euca_conf --list-nodes
echo's registered node
sudo euca_conf --deregister-nodes 10.0.0.2
sudo euca_conf --list-nodes
echo's registered node
sudo euca_conf --deregister-cluster cluster2011mrt
sudo euca_conf --register-cluster cluster2011mrt 10.0.0.2
sudo euca_conf --list-nodes
echo's nothing
sudo euca_conf --register-nodes 10.0.0.2
sudo euca_conf --list-nodes
echo's nothing
sudo euca_conf --deregister-cluster cluster2011mrt
sudo euca_conf --register-cluster cluster2011mrt 10.0.0.2
Needs time to do something! Then:
echo's ERROR: failed to register new cluster, please log in to the admin interface and check cloud status.
Few second's later, try again without workaround #9:
sudo euca_conf --register-cluster cluster2011mrt 10.0.0.2
echo's SUCCESS: new cluster ........

It looks it is time related on a old Intel XEON!