<br><br><div class="gmail_quote">On Sat, Oct 30, 2010 at 8:54 AM, Justin Riley <span dir="ltr"><<a href="mailto:jtriley@mit.edu">jtriley@mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"> On 10/29/10 8:07 PM, Dan Tenenbaum wrote:<br>
> Could this have something to do with the preparation that starcluster<br>
> does prior to creating an image?<br>
<br>
</div>Well if you didn't set disable_root: 0 then not being able to login as<br>
root is most likely because of that. Not being able to login as ubuntu<br>
user though *could* be caused by the cloud-init having a new behavior in<br>
10.10 that it does not setup /home/ubuntu/.ssh folder if it does not<br>
already exist (that is purely a guess, I haven't looked at the latest<br>
version of cloud-init since the 10.04 Alestic AMI). The preparation in<br>
starcluster 0.91.2's createimage command does blast all .ssh folders in<br>
/home before imaging so if the new cloud-init scripts do have this<br>
behavior then that would be why you can't login to ubuntu user after<br>
imaging with createimage.<br></blockquote><div><br></div><div>I ended up following the directions on the wiki, and using 10.04.. I did make the change setting disable_root to 0.</div><div><br></div><div>I had done the same thing on 10.10 but it didn't take for some reason.</div>
<div><br></div><div>Now I can ssh in to my instances as either root or sgeadmin, but when I start a cluster, I cannot ssh from master to a worker as sgeadmin without 1) being prompted about the key and 2) getting "permission denied (publickey)". I can work around this by doing all my work as root, but it's not ideal.</div>
<div><br></div><div>According to the logs, sgeadmin's rsa key is being created:<br><div>clustersetup.py:144 - INFO - Configuring passwordless ssh for user: sgeadmin</div><div>ssh.py:251 - DEBUG - True</div><div>ssh.py:251 - DEBUG - True</div>
<div>clustersetup.py:158 - DEBUG - Checking for orphaned private key file: /home/sgeadmin/.ssh/id_rsa | exists = True</div><div>clustersetup.py:160 - DEBUG - Removing orphaned private key file: /home/sgeadmin/.ssh/id_rsa</div>
<div>clustersetup.py:158 - DEBUG - Checking for orphaned private key file: /home/sgeadmin/.ssh/id_rsa.pub | exists = True</div><div>clustersetup.py:160 - DEBUG - Removing orphaned private key file: /home/sgeadmin/.ssh/id_rsa.pub</div>
<div>clustersetup.py:162 - INFO - Generating local RSA ssh keys for user: sgeadmin</div></div><div><br></div><div>id_rsa and id_rsa.pub DO exist in ~sgeadmin/.ssh on the master and workers.</div><div>So I"m not sure what's up with that.</div>
<div><br></div><div>Thanks</div><div>Dan</div><div><br></div></div>