Comment 2 for bug 430075
Revision history for this message
| Etienne Goyer (etienne-goyer-outlands) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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, despite that I did accept the package maintainer's version. Manually fixing the config file makes the eucalyptus-nc start, and I can fix the package installation with "apt-get install -f".