This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu6
---
eucalyptus (1.6~bzr854-0ubuntu6) karmic; urgency=low
[ Thierry Carrez ]
* Apply upstream rev867 and rev876 diffs to fix SC registration through
Web UI, LP: #436313
* tools/eucalyptus-java-ws.in: Reapply f
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
--
eucalyptus-nc fail to upgrade to 1.6~bzr746-0ubuntu1
https://bugs.launchpad.net/bugs/430075
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
I *think* the eucalyptus-nc init script needs to throw the error
message, and exit, but exit 0, to prevent this sort of upgrade problem.
* tools/eucalyptus-nc.in: eucalyptus not being configured is a fatal
condition for the init script, but exit 0 such that package installation
can proce
Confirming, marking High.
This is an area that we will need to test heavily (though we haven't
done so yet) ... users upgrading from Jaunty UEC to Karmic UEC.
Alternatively, we could document the gotchas, which might be sufficient
of the Jaunty UEC install base is small enough.
:-Dustin
** Chang
Got the same problem upgrading a Eucalyptus frontend (running -cloud,
-cc, -walrus and -sc). However, we cannot accept the package
maintainer's version, as it will overwrite the NODES value in the
configuration file, which would make the frontend consider there is no
node controller. People runni
The problem is indeed with eucalyptus. There is now a check in the init
script that will make it fail if the EUCALYPTUS value of the
configuration file is "not_configured". The config that shipped in the
last version indeed was. Somehow, the config file did not got upgraded
to the new version, d
The actual error:
EUCALYPTUS not configured!
invoke-rc.d: initscript eucalyptus-nc, action "start" failed.
This comes from the eucalyptus-nc init script
** Package changed: ubuntu => eucalyptus (Ubuntu)
--
eucalyptus-nc fail to upgrade to 1.6~bzr746-0ubuntu1
https://bugs.launchpad.net/bugs/43
