Recently I've stopped clobbering the node-preseed.conf quite as much,
and even with the CC's late_command the whole setup still has this
problem.
--
karmic cloud install fails at autodiscovery: wants both worlds (eucalyptus/root
users)
https://bugs.launchpad.net/bugs/480125
You received this
And to add insult to injury, it would appear that I have no NC lines in
euca-describe-availability-zones verbose after all that. It seems that
autodiscovery only *appeared* to complete.
--
karmic cloud install fails at autodiscovery: wants both worlds (eucalyptus/root
users)
After debugging with Dustin in IRC some this evening, it looks like this
is the result of some failure of the eucalyptus-udeb within my netboot
environment (or of the ordinary eucalyptus packages) to make the cloud
controller. If I purge and reinstall everything works as you'd expect
(but without
I agree there seems to be a mismatch in the instructions here. Assigning
Dustin since he authored most of that doc, he should be able to point to
an error in your procedure or his instructions.
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus
To clarify, I never managed to get the --no-rsync versions working.
Ultimately I managed to hack around this by symlinking the eucalyptus
user's id_rsa into root's .ssh/ dir and re-running sudo euca_conf
--discover-nodes.
** Description changed:
I have just installed two systems using karmic
I've linked it against the Karmic package. Upstream eucalyptus does not
have the --discover-nodes option and seems to be a UEC issue.
** Also affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
karmic cloud install fails at autodiscovery: wants both worlds
