[Bug 491254] Re: eucalyptus CLEAN=1 should also be supported in start

[Thierry Carrez]

** Description changed:

  CLEAN=1 support has been implemented as part of bug 460089, to avoid
  cleaning up the CC network state at each restart. A CLEAN=1 option was
  added to the post-stop in eucalyptus-cc.conf. A similar option should be
  added to the pre-start so that CLEAN=1 is also supported at start. That
  will mimic what the eucalyptus init script provides (cleanstart and
  cleanstop).
  
  ===============
  SRU Testing
  
  MINIMAL PATCH:
  http://bazaar.launchpad.net/~ubuntu-core-dev/eucalyptus/ubuntu-karmic/revision/727
  
  IMPACT:
-  When we converted the Eucalyptus init scripts to upstart jobs, we lost some functionality.  The initscripts supported a few additional actions, namely: cleanstop, cleanstart, cleanrestart.  These "clean" action would actually clear out the CC's state from /var/lib/eucalyptus/CC.  We should *not* do this in the default case, but we *should* provide a convenient, documented mechanism for administrators to do the "clean" restart process.  This update adds that functionality.
+  When we converted the Eucalyptus init scripts to upstart jobs, we lost some functionality.  The initscripts supported a few additional actions, namely: cleanstop, cleanstart, cleanrestart.  These "clean" action would actually clear out the CC's state from /var/lib/eucalyptus/CC.  We should *not* do this in the default case, but we *should* provide a convenient, documented mechanism for administrators to do the "clean" restart process.  This update restores that functionality.
  
  TEST CASE:
-  After installing/upgrading the -proposed eucalyptus packages:
-  1) Open a window on the CLC/CC, and watch the contents of /var/lib/eucalyptus/CC:
-   $ watch -n1 sudo ls -alF /var/lib/eucalyptus/CC
-  2) Perform each of the following actions, ensuring that the files in /var/lib/eucalyptus/CC are NOT removed:
-   $ sudo restart eucalyptus
-   $ sudo stop eucalyputs
-   $ sudo start eucalyptus
-   $ sudo restart eucalyptus-cc
-   $ sudo stop eucalyptus-cc
-   $ sudo start eucalyputs-cc
-  3) Now perform each of the following actions, ensure that the files in /var/lib/eucalyptus/CC ARE in fact removed at each operation:
-   $ sudo restart eucalyptus CLEAN=1
-   $ sudo stop eucalyputs CLEAN=1
-   $ sudo start eucalyptus CLEAN=1
-   $ sudo restart eucalyptus-cc CLEAN=1
-   $ sudo stop eucalyptus-cc CLEAN=1
-   $ sudo start eucalyputs-cc CLEAN=1
+  After installing/upgrading the -proposed eucalyptus packages:
+  1) Open a window on the CLC/CC, and watch the contents of /var/lib/eucalyptus/CC:
+   $ watch -n1 sudo ls -alF /var/lib/eucalyptus/CC
+  2) Perform each of the following actions, ensuring that the files in /var/lib/eucalyptus/CC are NOT removed:
+   $ sudo restart eucalyptus
+   $ sudo stop eucalyptus
+   $ sudo start eucalyptus
+   $ sudo restart eucalyptus-cc
+   $ sudo stop eucalyptus-cc
+   $ sudo start eucalytus-cc
+  3) Now perform each of the following actions, ensure that the files in /var/lib/eucalyptus/CC ARE in fact removed at each operation:
+   $ sudo restart eucalyptus CLEAN=1
+   $ sudo stop eucalyptus CLEAN=1
+   $ sudo start eucalyptus CLEAN=1
+   $ sudo restart eucalyptus-cc CLEAN=1
+   $ sudo stop eucalyptus-cc CLEAN=1
+   $ sudo start eucalyptus-cc CLEAN=1
  
  REGRESSION POTENTIAL:
  Regression potential is rather low.  The behavior is only changed when CLEAN=1 is passed to any of the eucalyptus scripts.  We have only recently documented this behavior.  It is intended to restore some functionality that was lost as of 9.10 GA when the eucalyptus init scripts were replaced by upstart jobs.
  ===============

-- 
eucalyptus CLEAN=1 should also be supported in start
https://bugs.launchpad.net/bugs/491254
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.