After purging and removing /var/lib/eucalyptus image store is out of sync

Bug #461202 reported by Torsten Spindler
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Build Version/Date: 1.6~bzr931-0ubuntu7
Environment used for testing: Ubuntu Karmic RC

Summary: After purging and removing /var/lib/eucalyptus image store is out of sync

Steps to Reproduce: Install UEC from packages, call aptitude purge on eucalyptus-[cc,cloud,sc,walrus], remove /var/lib/eucalyptus afterward

Expected result: image store is empty

Actual result: image store remembers latest downloaded images, but it's no longer there with euca-describe-images. The use case is that you want to create a new UEC from scratch after a failed attempt.

Revision history for this message
Mathias Gug (mathiaz) wrote :

Could you try to purge python-image-store-proxy as well?

To properly purge a UEC install I'd recommend to purge eucalyptus-common.

Changed in eucalyptus (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Torsten Spindler (tspindler) wrote : Re: [Bug 461202] Re: After purging and removing /var/lib/eucalyptus image store is out of sync

On Mon, 2009-10-26 at 16:20 +0000, Mathias Gug wrote:
> Could you try to purge python-image-store-proxy as well?
>
> To properly purge a UEC install I'd recommend to purge eucalyptus-
> common.

I purged both and reinstalled UEC. Now Firefox can't get to
https://127.0.0.1:8443 anymore.

Revision history for this message
Torsten Spindler (tspindler) wrote :

This is from /var/log/eucalyptus/httpd-cc_error_log

[Mon Oct 26 18:20:47 2009] [notice] caught SIGTERM, shutting down
[Mon Oct 26 18:22:33 2009] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0
configured -- resuming normal operations
[Mon Oct 26 18:22:36 2009] [error] server reached MaxClients setting,
consider raising the MaxClients setting
[Mon Oct 26 18:22:49 2009] [notice] caught SIGTERM, shutting down
[Mon Oct 26 18:24:34 2009] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0
configured -- resuming normal operations
[Mon Oct 26 18:24:37 2009] [error] server reached MaxClients setting,
consider raising the MaxClients setting
[Mon Oct 26 18:24:50 2009] [notice] caught SIGTERM, shutting down
[Mon Oct 26 18:26:36 2009] [notice] Apache/2.2.12 (Ubuntu) Axis2C/1.6.0
configured -- resuming normal operations
[Mon Oct 26 18:26:39 2009] [error] server reached MaxClients setting,
consider raising the MaxClients setting
[Mon Oct 26 18:26:52 2009] [notice] caught SIGTERM, shutting down

Revision history for this message
Torsten Spindler (tspindler) wrote :

According to cloud-debug.log there is a FileNotFoundException for
startup.groovy. I apt-file search'ed it and found it in
eucalyptus-java-common. But re-installing eucalyptus-java-common did not
succeed in getting the file back.

Excerpt from cloud-debug.log:

================================================================================
18:34:58 INFO [SystemBootstrapper:main] -> start: class com.eucalyptus.bootstrap.LocalDatabaseBootstrapper
18:34:58 DEBUG [GroovyUtil:main] java.io.FileNotFoundException: /etc/eucalyptus/cloud.d/scripts/startup.groovy (No such file or directory)
java.io.FileNotFoundException: /etc/eucalyptus/cloud.d/scripts/startup.groovy (No such file or directory)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:137)
        at java.io.FileInputStream.<init>(FileInputStream.java:96)
        at java.io.FileReader.<init>(FileReader.java:58)
        at com.eucalyptus.util.GroovyUtil.evaluateScript(GroovyUtil.java:45)
        at com.eucalyptus.bootstrap.LocalDatabaseBootstrapper.start(LocalDatabaseBootstrapper.java:172)
        at com.eucalyptus.bootstrap.SystemBootstrapper.start(SystemBootstrapper.java:207)
18:34:58 FATAL [LocalDatabaseBootstrapper:main] com.eucalyptus.util.FailScriptFailException: Executing the requested script failed: startup.groovy
com.eucalyptus.util.FailScriptFailException: Executing the requested script failed: startup.groovy
        at com.eucalyptus.util.GroovyUtil.evaluateScript(GroovyUtil.java:48)
        at com.eucalyptus.bootstrap.LocalDatabaseBootstrapper.start(LocalDatabaseBootstrapper.java:172)
        at com.eucalyptus.bootstrap.SystemBootstrapper.start(SystemBootstrapper.java:207)
Caused by: java.io.FileNotFoundException: /etc/eucalyptus/cloud.d/scripts/startup.groovy (No such file or directory)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:137)
        at java.io.FileInputStream.<init>(FileInputStream.java:96)
        at java.io.FileReader.<init>(FileReader.java:58)
        at com.eucalyptus.util.GroovyUtil.evaluateScript(GroovyUtil.java:45)
        ... 2 more
18:34:58 DEBUG [EntityWrapper:Thread-14] :1256578432.0000:db/EntityWrapper.<init>.106:eucalyptus:eucalyptus:CREATE:END:27:eucalyptus_storage:edu.ucsb.eucalyptus.storage.BlockStorageChecker.cleanStuckVolumes(BlockStorageChecker.java:137):29c2d3fa-1307-4968-92eb-6d2a1f443ba3:
18:34:58 DEBUG [EntityWrapper:Thread-14] :1256578432.0000:db/EntityWrapper.<init>.106:eucalyptus:eucalyptus:CREATE:END:2:eucalyptus_storage:edu.ucsb.eucalyptus.storage.BlockStorageChecker.cleanFailedVolumes(BlockStorageChecker.java:156):ad847f23-f446-4051-b22e-70bd4220c295:

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

<dotCOMmie> I seem to have trace down what causes https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/461202
<dotCOMmie> When purging "eucalyptus-common eucalyptus-cloud eucalyptus-walrus eucalyptus-sc eucalyptus-cc eucalyptus-nc" files are deleted which belong to eucalyptus-java-common
<dotCOMmie> These are files under /etc and are not removed by eucalyptus-java-common on "uninstall" of this package, which is triggered by above action
<dotCOMmie> so when re-installing those packages these files in /etc are not put back by eucalyptus-java-common (this package going from u to i)
<dotCOMmie> The work around is to use "aptitude --purge-unused purge eucalyptus-common eucalyptus-cloud eucalyptus-walrus eucalyptus-sc eucalyptus-cc eucalyptus-nc"
<dotCOMmie> which purges all dependent packages which would simply have been uninstalled otherwise

Changed in eucalyptus (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

This appears to be fixed in Lucid.

I just did the following on an up-to-date Lucid, and did not encounter a problem:

sudo apt-get purge euca2ools eucalyptus-cc eucalyptus-cloud eucalyptus-common eucalyptus-gl eucalyptus-java-common eucalyptus-sc eucalyptus-walrus python-image-store-proxy
...
sudo apt-get install euca2ools eucalyptus-cc eucalyptus-cloud eucalyptus-common eucalyptus-gl eucalyptus-java-common eucalyptus-sc eucalyptus-walrus python-image-store-proxy

Please reopen this bug if you can still reproduce this.

Changed in eucalyptus (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Reproduce this on current Lucid, that is.

Revision history for this message
Thierry Carrez (ttx) wrote :

This happens if you purge eucalyptus-common /without/ purging eucalyptus-java-common or image-store-proxy:

sudo apt-get purge eucalyptus-cc eucalyptus-cloud eucalyptus-common eucalyptus-gl eucalyptus-sc eucalyptus-walrus
...
sudo apt-get install eucalyptus-cc eucalyptus-cloud eucalyptus-common eucalyptus-gl eucalyptus-sc eucalyptus-walrus

Then eucalyptus-common postrm purges /etc/eucalyptus and /var/lib/eucalyptus, where files from image-store-proxy and eucalyptus-java-common live.

Changed in eucalyptus (Ubuntu):
status: Fix Released → Triaged
Revision history for this message
Thierry Carrez (ttx) wrote :

See bug 503063 for the issue affecting /etc/eucalyptus (instead of /var/lib/eucalyptus)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.