** Tags added: iso-testing
--
Autoregistration of eucalyptus-cc sometimes fails
https://bugs.launchpad.net/bugs/438602
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
The dbus-reconnect fix that I assume the Upstart task refers to has been
uploaded
** Changed in: upstart (Ubuntu Karmic)
Status: Incomplete = Fix Released
--
Autoregistration of eucalyptus-cc sometimes fails
https://bugs.launchpad.net/bugs/438602
You received this bug notification
Documented workaround for eucalyptus 1.6~bzr854-0ubuntu12 users:
$ sudo euca_conf --local-sync --register-walrus IPADDRESSOFTHECLUSTER
$ sudo euca_conf --local-sync --register-cluster CLUSTERNAME
IPADDRESSOFTHECLUSTER
$ sudo euca_conf --local-sync --register-sc CLUSTERNAME
IPADDRESSOFTHECLUSTER
I've made some progress, and autoregistration is now succeeding for me.
I had to ditch the localhost registrations, and use a real IP address.
I pulled that functionality into a single place, that can be sourced by
each upstart file.
As of 1am, this is working for me.
I'm uploading now, and
This bug was fixed in the package eucalyptus - 1.6~bzr854-0ubuntu13
---
eucalyptus (1.6~bzr854-0ubuntu13) karmic; urgency=low
* eucalyptus-common.eucalyptus.upstart: the -L option was in the wrong
place, breaking the console.log logging, LP: #439161
*
We're having trouble getting in touch with Scott today, but what we're
seeing now is starting to look like an Upstart deficiency. I'm marking
a task against Upstart with this bug, in case there's a bug there.
We think we have the registration correctly configured using upstart,
specifying the
It seems that the eucalyptus-cc-registration job is not always started
by upstart.
To check that the jobs have been started, I've added a pre-start section
to each -registration job (ex for the walrus-registration job):
pre-start script
touch /var/tmp/walrus-registration.started
end
