Walrus, SC and CC registrations hardcode 'localhost'

Bug #437058 reported by Matt Zimmerman on 2009-09-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Dustin Kirkland 

Bug Description

Dustin is working on automating the registration step, but the approach we're using for now only works for the (default) case where the walrus is on the same system as the eucalyptus frontend. This is a reminder to fix that down the road.

ProblemType: Bug
Architecture: i386
Date: Fri Sep 25 20:43:18 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: eucalyptus-walrus (not installed)
 PATH=(custom, user)
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SourcePackage: eucalyptus
Tags: ubuntu-unr
Uname: Linux 2.6.31-10-generic i686

Changed in eucalyptus (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Matt Zimmerman (mdz) on 2009-09-28
summary: - Walrus registration assumes that walrus is running on the same host as
- the frontend
+ Automated registration assumes that walrus, SC and CC are running on the
+ same host as the CLC
Dustin Kirkland  (kirkland) wrote :

So the first, most basic aspect of this problem is that these components assume that they should register as 'localhost', or the same system running the CLC.

This assumption actually appears to be part of our problem with automatic registration.

When I used the real, external IP address in the upstart scripts, I got the following in my logs:

root@cloud:/etc/init# tail -n1 /var/log/eucalyptus/*regist*
==> /var/log/eucalyptus/cc-registration.log <==
SUCCESS: new cluster 'canyonedge' on host '' successfully registered.

==> /var/log/eucalyptus/sc-registration.log <==
SUCCESS: new SC for cluster 'canyonedge' on host '' successfully registered.

==> /var/log/eucalyptus/walrus-registration.log <==
SUCCESS: new walrus on host '' successfully registered.

Changed in eucalyptus (Ubuntu):
assignee: nobody → Dustin Kirkland (kirkland)
status: Triaged → In Progress
summary: - Automated registration assumes that walrus, SC and CC are running on the
- same host as the CLC
+ Walrus, SC and CC registrations hardcode 'localhost'
Dustin Kirkland  (kirkland) wrote :

I'm going to "solve" this by putting a sourceable script at /etc/eucalyptus/eucalyptus-ipaddr.conf (like eucalyptus-cc.conf), where some variables can be set, such as:


For now, all of these are going to be the same thing (the external IP of the local system).

But in the future, we can modify this script to use avahi and discover these services, or use debconf and allow the admin to manually configure them and set them in this file.


Changed in eucalyptus (Ubuntu):
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu13

eucalyptus (1.6~bzr854-0ubuntu13) karmic; urgency=low

  * eucalyptus-common.eucalyptus.upstart: the -L option was in the wrong
    place, breaking the console.log logging, LP: #439161
  * eucalyptus-cc.eucalyptus-cc-registration.upstart,
    eucalyptus-cc.upstart, eucalyptus-cloud.upstart,
    eucalyptus-ipaddr.conf, eucalyptus-common.install,
    eucalyptus-sc.upstart, eucalyptus-walrus.upstart: using "localhost"
    is breaking registration; instead, use the real, external ip
    address; consolidate the (nasty) logic for determining this
    into a single, sourcable, overridable location, LP: #437058, #438602
  * 80-eucalyptus-url: use the new $CLOUD_IP_ADDR value and logic

 -- Dustin Kirkland <email address hidden> Wed, 30 Sep 2009 01:16:12 -0500

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

Other bug subscribers