ow2-proactive
SSHInfrastructure shows authentication error even if RMNode machines are accessible through SSH
Original issue created by Mauricio Jost on 10, Jan 2015 at 04:12 AM - SCHEDULING-2213
Assume hosts A and B. A with RM, B with a RMNode. If we want to deploy a node in B using SSHInfrastructure, we need to make sure A contains both, private key, and public key (?) in ~/.ssh/. Why the need of the public key? And the error message is not trivial.
To reproduce it: Prepare host A and host B. A would have RM and B would be the node. Put id_rsa in host A, in its default location (~/.ssh/). Put content of id_rsa.pub in B (~/.ssh/authorized_keys). B should be accessible from A through SSH command. Remove from A the file ~/.ssh/id_rsa.pub, B will be accessible from A (through SSH), but still the SSHInfrastructure trying to deploy an RMnode in B will fail with a useless wrong message:
{noformat] Node SSH-Compute-38 URL : deploying://Compute/SSH-Compute-38 Node source : Compute Provider : admin State : Lost Description : SSH command failed to launch node on host 172.28.128.6
Error code: 2 Errput: [E] Authentication failed Output: Command : /usr/lib/jvm/java-7-openjdk-amd64//bin/java -Djava.security.policy=/home/proactive/opt/scheduling//config/security.java.policy-client -Dlog4j.configuration=file:/home/proactive/opt/scheduling//config/log/node.properties -Dpas.launcher.forkas.method=pwd -cp .:/home/proactive/opt/scheduling/addons:/home/proactive/opt/scheduling/dist/lib/* org.ow2.proactive.resourcemanager.utils.RMNodeStarter -v [OBFUSCATED_CRED] -n SSH-Compute-38 -s Compute -r pnp://vagrant-ubuntu-trusty-64:64738/ -p 30000 {noformat}
Original comment posted by Youri Bonnaffe on 12, Jan 2015 at 09:47 AM
Probably related to code in programming-core, classes like SshConfig/SshKeys that reads public/private keys
The bug applies to SSHInfrastructure only, not SSHInfrastructureV2.
