Not obvious a "Clean" restart is needed after config changes

[Thierry Carrez]

On regular restarts (once bug 460089 is fixed) the CC will retain network state so that active VMs can continue to run.
If the CC network configuration is changed in /etc/eucalyptus/eucalyptus.conf, "restart eucalyptus" will not be enough to take it into account. You'll have to pass CLEAN=1 to the job (maybe rebooting works).

We might need to make it more apparent to the user, by providing a eucalyptus-clean-network-state script and documenting its use in eucalyptus.conf and elsewhere.

[Dustin Kirkland  (kirkland)]

I'm actually raising this priority to High.

I've been struggling with this (silly) problem for a couple of days now, wondering why my changes aren't taking effect.

This should be documented in the manpage, and *possibly* in line in the eucalyptus.(local.)conf files. We should knock this out at the sprint.

[Launchpad Janitor (janitor)]

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

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

  * clc/modules/www/src/main/java/edu/ucsb/eucalyptus/admin/client/EucalyptusWebInterface.java:
    use upstream's better method of getting the version displayed in the web
    login page
  * tools/euca_conf.in: add known_hosts -> /dev/null to the SCP_OPT
  * debian/eucalyptus-common.eucalyptus.upstart: allow for simple
    eucalyptus process management with 'start,stop,status' of 'eucalyptus'
    by ensuring that a dummy sleep process at least runs when the cc or
    nc are started, LP: #504521, #504704
  * debian/eucalyptus-cc.upstart, debian/eucalyptus.conf,
    tools/eucalyptus.conf.5: document CC clean restart, LP: #464384
 -- Dustin Kirkland <email address hidden> Wed, 03 Feb 2010 13:59:37 -0800