Lucid: walrus not automatically discovered

[Torsten Spindler]

I just installed UEC with the Lucid installer. First I installed the front end with clc, walrus, cc and sc. Then the node. The node told me that it cannot find walrus and the installer suggested to me to install it first.

I checked ps aux | grep avahi on the frontend and the avahi line for walrus looks different from the others. It says avahi-publish -s 192.168.1.120 instead of avahi-publish -s TestCloud.

[Dustin Kirkland  (kirkland)]

Thanks for the report.

We're working hard on autoregistration for Lucid. We'll take a look at this problem as soon as the Lucid autoregistration code is ready for some exercise.

[Colin Watson (cjwatson)]

The -s argument shouldn't matter, for what it's worth. The important thing is just that it has type=walrus.

When the node installation fails, could you switch to tty2 and run 'EUCA_FIND_COMPONENT_DEBUG=1 euca_find_component walrus', and copy the output here? You might have to transcribe the output manually; sorry about that if so.

[Torsten Spindler (tspindler)]

I cannot repeat the problem today.

After specifying the hostname to 'node01' the next screeen says 'Select
cloud installation mode' and informs that no eucalyptus cloud controller
was found on your network. Albeit the cloud controller is up and running
on another machine. I then specify the cloud controller's IP address.
Today I get the suggestion 'Node controller', which is correct.