eucalyptus-cc postinst fails without node controllers defined

[Chris Jones]

When installing eucalyptus-cc, -cloud, -common and -gl I am left with -cc and -cloud unconfigured because of:

Setting up eucalyptus-cc (1.5~bzr198-0ubuntu1) ...
Restarting Eucalyptus services: NODES is empty in configuration file!
invoke-rc.d: initscript eucalyptus, action "reload" failed.
dpkg: error processing eucalyptus-cc (--configure):
 subprocess post-installation script returned error exit status 1

[Chris Jones (cmsj)]

Editing /etc/eucalyptus/eucalyptus.conf and giving it a hostname for the node controller in the NODES="" section allows this to complete.

I suppose the ideal scenario would be for eucalyptus to start with no node controllers configured, but failing that, perhaps this should be prompted for with debconf?

[Chris Jones (cmsj)]

per discussions with Soren - this is actually just the init script performing sanity checks on the init script. It should print a warning instead of forcibly exiting when NODES is empty.

[Launchpad Janitor (janitor)]

This bug was fixed in the package eucalyptus - 1.5~bzr198-0ubuntu2

---------------
eucalyptus (1.5~bzr198-0ubuntu2) jaunty; urgency=low

  * Make sure rootwrap binary gets its ownership and mode applied
    immediately.
  * Correctly set EUCA_USER from -common's postinst. (LP: #333341)
  * Don't fail in the init script if NODES is empty. (LP: #333333)

 -- Soren Hansen <email address hidden> Mon, 23 Feb 2009 20:42:24 +0100