upstart scripts expect cloud/cc/sc/walrus all on the same system
Bug #450777 reported by
Dustin Kirkland
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Medium
|
Dustin Kirkland |
Bug Description
The cc/sc/walrus upstart scripts were written with the expectation that all of these components would be installed on the same system as the cloud controller.
As such, the registration jobs wait for the eucalyptus-cloud service to start. However, this won't occur in multi-component setups.
We need to shift the dependency to "starting eucalyptus-
:-Dustin
Changed in eucalyptus (Ubuntu): | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
assignee: | nobody → Dustin Kirkland (kirkland) |
To post a comment you must log in.
This bug was fixed in the package eucalyptus - 1.6~bzr930-0ubuntu1
--------------- 0ubuntu1) karmic; urgency=low
eucalyptus (1.6~bzr930-
[ Dustin Kirkland ] eucalyptus- url, debian/ eucalyptus- cc.install, eucalyptus- cc.links, debian/ eucalyptus- cc.postinst: : eucalyptus- udeb.finish- install: fix typo; fix breakage of network/ interfaces when nodes are configured with static IP cc.upstart, cloud.eucalyptu s-cc-registrati on.upstart, cloud.eucalyptu s-sc-registrati on.upstart, cloud.eucalyptu s-walrus- registration. upstart, sc.upstart, eucalyptus- walrus. upstart, rules, control: eucalyptus- ipaddr. conf: update inline documentation accordingly eucalyptus- cc.templates: update public_ips instructions in the common. eucalyptus. upstart: fix unclean package purging,
* debian/
debian/
- fix whitespace, to match other update-motd urls LP: #450449
- link to ubuntu.com/cloud, which links to our documentation,
necessary for new UEC admins
- ensure that it gets installed with executable permissions,
LP: #444970
* debian/
/etc/
addresses, LP: #446023
* eucalyptus-
eucalyptus-
eucalyptus-
eucalyptus-
eucalyptus-
- registration of cc/sc/walrus should *only* ever occur on the CLC,
so these scripts should be moved to the eucalyptus-cloud package,
LP: #450815
- starting cc/sc/walrus should *not* depend on eucalyptus-cloud
running, since these components can be installed on separate
machines, LP: #450777
- but if cc/sc/walrus are on a system doing registration, ensure that
these jobs kick off when "starting" registration
- allow for whitespace separated list of $CC_IP_ADDR and $SC_IP_ADDR,
as there can be more than one of these, and admins in multi-cluster
or multi-component mode would need to register a list
- use Replaces to ensure upgrades work properly
* debian/
* debian/
installer to match the new upstream implementation, LP: #438565
* eucalyptus-
which hangs on stopping eucalyptus service
[ Upstream ] PUBLICIPS field of eucalyptus.conf NOVLAN, when ...
* Merge upstream revision 930
* This snapshot is expected to fix the following bugs:
- LP: #449944 - fixes remote component bootstrap issue
- LP: #430852, #401996 - fix handling of security groups for the admin
- LP: #449948 - fix issues with network index and address recovery after
a system restart
- LP: #398867 - fix storing VLAN tag info from web ui
- LP: #430266 - fix setting of HTTP error codes
- LP: #449948 - part of fix to LP:#449948 the CC now correctly sets the
networkIndex field in the reponse message of describeInstances
- LP: #438565 - allowing a range of IPs to be specified in the
VNET_
- LP: #449143 - Add the 169.254.169.254 address to eth0 as 'scope link'
in order to avoid conflict with the UEC avahi-publish mechanism
- LP: #449135 - Prevents a segfault in CC during client connection to NC
on describeInstances, when number of instances is high (> 20 or so).
The number of bytes sent to 'malloc' was being calculated incorrectly.
- LP: #444838 - fix to fully allow VMs to access meta-data service in
MANAGED-