| 2010-02-02 15:21:07 |
Boris Devouge |
bug |
|
|
added bug |
| 2010-02-06 07:26:48 |
Dustin Kirkland |
eucalyptus (Ubuntu): importance |
Undecided |
High |
|
| 2010-02-06 07:26:50 |
Dustin Kirkland |
eucalyptus (Ubuntu): importance |
High |
Medium |
|
| 2010-02-06 07:26:54 |
Dustin Kirkland |
eucalyptus (Ubuntu): status |
New |
Triaged |
|
| 2010-02-06 07:26:55 |
Dustin Kirkland |
eucalyptus (Ubuntu): assignee |
|
Dustin Kirkland (kirkland) |
|
| 2010-02-06 07:31:19 |
Dustin Kirkland |
eucalyptus (Ubuntu): status |
Triaged |
Fix Released |
|
| 2010-02-22 20:46:47 |
Dustin Kirkland |
nominated for series |
|
Ubuntu Karmic |
|
| 2010-02-22 20:46:47 |
Dustin Kirkland |
bug task added |
|
eucalyptus (Ubuntu Karmic) |
|
| 2010-02-22 20:46:47 |
Dustin Kirkland |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-02-22 20:46:47 |
Dustin Kirkland |
bug task added |
|
eucalyptus (Ubuntu Lucid) |
|
| 2010-02-22 20:46:59 |
Dustin Kirkland |
eucalyptus (Ubuntu Karmic): status |
New |
In Progress |
|
| 2010-02-22 20:47:06 |
Dustin Kirkland |
eucalyptus (Ubuntu Karmic): importance |
Undecided |
Medium |
|
| 2010-02-22 20:47:11 |
Dustin Kirkland |
eucalyptus (Ubuntu Karmic): assignee |
|
Dustin Kirkland (kirkland) |
|
| 2010-03-01 18:24:36 |
Dustin Kirkland |
eucalyptus (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
| 2010-03-01 18:35:03 |
Dustin Kirkland |
description |
Please see initial issue reported here:
http://open.eucalyptus.com/forum/walrus-configuration-failed-contact-server
When running Walrus/S3 services of a different machine than the Cloud controller (CLC), we are missing some jar files. We seems to assume that the Walrus/S3 services are running out of the CLC by default.
From the earlier referenced page:
"There is an issue, however, with starting standalone Eucalyptus components due to a missing file in the Ubuntu Karmic packages (we, the upstream, do not produce those packages).
Try purging all eucalyptus packages, go through the steps again, then manually copy /usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar from the CLC host to /usr/share/eucalyptus on the Walrus host, run "stop eucalyptus" and then "start eucalyptus" on the Walrus host."
Copying the /usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar to the walrus host fixes the problem. |
Please see initial issue reported here:
http://open.eucalyptus.com/forum/walrus-configuration-failed-contact-server
When running Walrus/S3 services of a different machine than the Cloud controller (CLC), we are missing some jar files. We seems to assume that the Walrus/S3 services are running out of the CLC by default.
From the earlier referenced page:
"There is an issue, however, with starting standalone Eucalyptus components due to a missing file in the Ubuntu Karmic packages (we, the upstream, do not produce those packages).
Try purging all eucalyptus packages, go through the steps again, then manually copy /usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar from the CLC host to /usr/share/eucalyptus on the Walrus host, run "stop eucalyptus" and then "start eucalyptus" on the Walrus host."
Copying the /usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar to the walrus host fixes the problem.
=================
SRU NOTES
* Impact
* This bug affects any users where the eucalyptus-cloud package is installed on a separate system from other Eucalyptus components.
* How Addressed
* The eucalyptus-interface jar should be installed by the eucalayptus-java-common package, rather than the eucalyptus-cloud package.
* Minimal Patch
diff -u eucalyptus-1.6~bzr931/debian/eucalyptus-cloud.install eucalyptus-1.6~bzr931/debian/eucalyptus-cloud.install
--- eucalyptus-1.6~bzr931/debian/eucalyptus-cloud.install
+++ eucalyptus-1.6~bzr931/debian/eucalyptus-cloud.install
@@ -3 +2,0 @@
-/usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar
diff -u eucalyptus-1.6~bzr931/debian/eucalyptus-java-common.install eucalyptus-1.6~bzr931/debian/eucalyptus-java-common.install
--- eucalyptus-1.6~bzr931/debian/eucalyptus-java-common.install
+++ eucalyptus-1.6~bzr931/debian/eucalyptus-java-common.install
@@ -10,6 +10,7 @@
/usr/share/eucalyptus/eucalyptus-clustermgr-1.6-devel.jar
/usr/share/eucalyptus/eucalyptus-keymgr-1.6-devel.jar
/usr/share/eucalyptus/eucalyptus-config-1.6-devel.jar
+/usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar
/etc/eucalyptus/cloud.d
/usr/lib/eucalyptus/liblvm2control.so
/var/lib/eucalyptus/modules
* Reproduce Instructions
* Install the eucalyptus-cloud on one system, and any of (eucalyptus-walrus, eucalyptus-sc, eucalyptus-cc) on a different system. Note that the file /usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar is missing on any of the systems where eucalyptus-cloud is NOT installed.
* Upgrade to the new packages. Note that /usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar is now installed by eucalyptus-java-common with:
* dpkg -S /usr/share/eucalyptus/eucalyptus-interface-1.6-devel.jar
* Regression Potential
* Minimal, I believe.
* NB: One question for the SRU team... Is any debian/control magic required since we've moved the installation of this file from one binary package to another? It appears to me that upgrades are handled cleanly without it (at least the testing that I did).
================= |
|
| 2010-03-04 09:42:25 |
Martin Pitt |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
In Progress |
|
| 2010-03-04 17:15:12 |
Martin Pitt |
eucalyptus (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
| 2010-03-04 17:15:19 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2010-03-04 18:14:21 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-proposed/eucalyptus |
|
| 2010-04-13 09:52:33 |
Martin Pitt |
tags |
verification-needed |
verification-done |
|
| 2010-04-13 09:53:21 |
Launchpad Janitor |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
