[Bug 480125] Re: karmic cloud install fails at autodiscovery: wants both worlds (eucalyptus/root users)
Nick Moffitt
nick at canonical.com
Wed Nov 11 13:29:38 GMT 2009
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 over PXEboot. Both were
given the anna/choose_modules=eucalyptus-udeb boot option.
The Node Controller box was given the preseed config line:
- d-i eucalyptus/install-mode string Node
+ d-i eucalyptus/install-mode string Node
The Cluster Controller box was given:
- d-i eucalyptus/install-mode string Cluster
+ d-i eucalyptus/install-mode string Cluster
As well as appropriate settings for eucalyptus/cluster-name,
eucalyptus/publicips, and eucalyptus/private-interface.
After boot, I followed the instructions from
https://help.ubuntu.com/community/UEC/NodeInstallation to use ssh-copy-
id to get the eucalyptus pubkey from the CC to the NC. I then tried the
instructions from https://help.ubuntu.com/community/UEC/CDInstall to
autodiscover nodes with:
- sudo euca_conf --no-rsync --discover-nodes
+ sudo euca_conf --no-rsync --discover-nodes
My NC was found, and I accepted the prompt to proceed to add it. The
scp failed, because root does not have the eucalyptus user's key. I
then tried:
- sudo -u eucalyptus euca_conf --no-rsync --discover-nodes
+ sudo -u eucalyptus euca_conf --discover-nodes
And this succeeded in copying keys around, but failed when it tried to
edit /etc/eucalyptus/eucalyptus.conf because that is owned by root.
This seems to be a fairly grave problem in either the instructions or
the euca_conf program. At the moment, though, I'd appreciate a helpful
workaround. How am I to get my NC added?
--
karmic cloud install fails at autodiscovery: wants both worlds (eucalyptus/root users)
https://bugs.launchpad.net/bugs/480125
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
More information about the Ubuntu-server-bugs
mailing list