Autoregistration: Node doesn't ask for a specific cluster to be registered in

Bug #515812 reported by Thierry Carrez on 2010-02-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Thierry Carrez
Thierry Carrez

Bug Description

Node doesn't advertise which cluster it wants to associate with, which can break in multicluster, single network configurations.

This needs to be fixed in three areas:
- NC postinst should create a file containing node name
- NC publication job should read that file and advertise target cluster
- Node autoregistration script should check that the node actually wants to register with us

Thierry Carrez (ttx) on 2010-02-02
Changed in eucalyptus (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Thierry Carrez (ttx)
Thierry Carrez (ttx) on 2010-02-02
Changed in eucalyptus (Ubuntu Lucid):
milestone: none → lucid-alpha-3
Thierry Carrez (ttx) on 2010-02-12
Changed in eucalyptus (Ubuntu Lucid):
status: Triaged → In Progress
Thierry Carrez (ttx) on 2010-02-15
Changed in eucalyptus (Ubuntu Lucid):
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 1.6.2~bzr1189-0ubuntu2

eucalyptus (1.6.2~bzr1189-0ubuntu2) lucid; urgency=low

  * Make node ask to be registered in a specific cluster (LP: #515812):
    - debian/eucalyptus-nc.postinst: Store target cluster name, if any
    - debian/eucalyptus-nc.eucalyptus-nc-publication.upstart: Use stored target
      cluster name in node publication
    - debian/registration/node: Only register if we are on target cluster
 -- Thierry Carrez <email address hidden> Mon, 15 Feb 2010 17:49:07 +0100

Changed in eucalyptus (Ubuntu Lucid):
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