Ubuntu
eucalyptus package

Autoregister runs euca_conf with "localhost" but that is refused in 1.6~bzr808

Bug #434593 reported by Thierry Carrez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
Medium
Matt Zimmerman
Ubuntu ubuntu-9.10-beta
Karmic
Fix Released
Medium
Matt Zimmerman
Ubuntu ubuntu-9.10-beta

Bug Description

register_local_cloud in the initscripts tries (for example) "euca_conf --register-walrus localhost" to register components.
It used to work in 1.6~bzr746-0ubuntu3.
With 1.6~bzr808-0ubuntu1, it fails with the following error:
Components cannot be registered using local, link-local, or multicast addresses.

We need to find a way to autoregister components with the correct external IP address, or drop autoregistering altogether.

See original description
Tags: eucalyptus

Related branches

lp:~mdz/eucalyptus/plumbers
Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-9.10-beta
status: New → Triaged
tags: added: eucalyptus
Revision history for this message
Thierry Carrez (ttx) wrote :

It's now explicitely refused in upstream code, from rev756 on in
clc/modules/configuration/src/main/java/com/eucalyptus/config/Configuration.java

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

To be more precise, it's coming from rev774 on clc/modules/msgs/src/main/java/com/eucalyptus/util/NetworkUtil.java:
http://bazaar.launchpad.net/~eucalyptus-maintainers/eucalyptus/1.6/revision/774#clc/modules/msgs/src/main/java/com/eucalyptus/util/NetworkUtil.java
It was a fix for bug 431934, the fact that it worked was indeed a bug.

summary: - euca_conf --register-walrus localhost fails in 1.6~bzr808
+ Autoregister runs euca_conf --register-walrus localhost but that is
+ refused in 1.6~bzr808
description: updated
summary: - Autoregister runs euca_conf --register-walrus localhost but that is
- refused in 1.6~bzr808
+ Autoregister runs euca_conf with "localhost" but that is refused in
+ 1.6~bzr808
Revision history for this message
Thierry Carrez (ttx) wrote :

This can be workarounded by manually registering components (on the web UI or the CLI)
sudo euca_conf --local-sync --register-walrus <externalIP>

Changed in eucalyptus (Ubuntu Karmic):
importance: High → Medium
Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu Karmic):
assignee: nobody → Thierry Carrez (ttx)
Revision history for this message
Colin Watson (cjwatson) wrote :

Should we just use VNET_PUBINTERFACE here, at least for now?

Matt Zimmerman (mdz)
Changed in eucalyptus (Ubuntu Karmic):
assignee: Thierry Carrez (ttx) → Matt Zimmerman (mdz)
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

  [ Dustin Kirkland ]
  * debian/control: drop dhcp from -nc's recommends, add it to -cc's
    recommends, LP: #364925
  * tools/euca_conf.in: use "-oStrictHostKeyChecking=no" if we're doing
    --discover-nodes, LP: #436210
  * debian/eucalyptus-udeb.finish-install: add own ssh host key to
    /etc/ssh/ssh_known_hosts, LP: #436211

  [ Colin Watson ]
  * euca_find_cluster: Use the proper bracketed format for IPv6 host/port
    combinations.
  * euca_find_cluster: For now, only ask for an IPv4 address for the
    cluster, as IPv6 addresses often show up by accident but don't work, and
    we don't have time to deal with this right now (LP: #436200).
  * tools/eucalyptus-java-ws.in: Increase timeout here too, to go with
    Matt's previous change.

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

  * Temporarily disable rejection of loopback addresses in registerComponent.
    This seems perfectly valid when the cloud and cluster controllers are
    running on the same system.

    This works around LP: #434593 (which is a blocker for 9.10 beta) and
    reopens LP: #431934 (which is not)
  * tools/eucalyptus-cc.in:register_local_cloud: Increase the timeout
    waiting for the service to start before registering it. Increasing from 10
    seconds to 60 seems to be sufficient to work around LP: #434590

 -- Colin Watson <email address hidden> Fri, 25 Sep 2009 15:30:36 +0100

Changed in eucalyptus (Ubuntu Karmic):
status: In Progress → 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.