UEC will accepts empty name for a cluster

Bug #455062 reported by graziano obertelli on 2009-10-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)

Bug Description

Using UEC to install a cluster: the question about the cluster name will accept an empty string, which will prevent the registration of the CC and the SC, thus having a non-functional installation at the end. Perhaps the question should have a default (for example the hostname)?

Thierry Carrez (ttx) wrote :

Note that if there is an easy and non-damaging way to change the cluster name once its installed, we could even skip the question altogether and default to the hostname.

Changed in eucalyptus (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Dustin Kirkland  (kirkland) wrote :

I recently committed a fix for Bug #513379, which is related. In this fix, basically, we default the cluster name to "cluster1", which should avoid *most* situations where the cluster name is blank (except for places where users intentionally blank the cluster name, which still might need to be solved). Feel free to reopen this bug report if you do not feel that this sufficiently solves the issue.

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

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

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

  [ Thierry Carrez ]
  * debian/control, debian/build-jars, debian/eucalyptus-java-common.links:
    Migrate from jetty6 to jetty (LP: #418836)

  [ Dustin Kirkland ]
  * debian/eucalyptus-url: conditionally print the CLC's ipaddress in the MOTD
    only if we're on the CLC, LP: #494808
  * debian/eucalyptus-cc.config: default the cluster-name to "cluster1",
    ideally to eliminate one mostly unneeded (but preseedable) debconf
    question, LP: #513379, #455062
 -- Dustin Kirkland <email address hidden> Mon, 01 Feb 2010 22:07:49 -0800

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