Bug #5134
closed
Unable to launch official-slcc-5x-x86-64
Added by Schwarz Lionel over 11 years ago.
Updated over 9 years ago.
Description
Connecting to 134.158.246.64 on port 22.
Connected via SSH.
Authenticating as jenkins
Authentication failed. Trying again...
Authenticating as jenkins
Authentication failed. Trying again...
Authenticating as jenkins
Authentication failed. Trying again...
Authenticating as jenkins
Authentication failed. Trying again...
Authenticating as jenkins
Authentication failed. Trying again...
Authenticating as jenkins
Authentication failed. Trying again...
Authenticating as jenkins
java.io.IOException: Publickey authentication failed.
- Priority changed from High to Low
Not sure official-SLCC-5x-x86_64 is not a test image.
INFO: << (root:rsa[fingerprint(0e:20:61:cc:e2:f9:af:e7:ac:a4:d8:5c:37:e8:3d:c5),sha1(c1:e5:62:7c:67:c5:c0:72:fe:91:4a:48:18:a4:00:00:58:ed:0f:fe)]@134.158.246.65:22)
error acquiring
{hostAndPort=134.158.246.65:22,
loginUser=root,
ssh=null,
connectTimeout=60000,
sessionTimeout=60000}
(attempt 1 of 7): Exhausted available authentication methods
- Status changed from New to Assigned
- Assigned To set to Schwarz Lionel
1) AuthorizationException on node regionOne/ed1b5b79-3686-4c71-9631-b1e506eafb26:
org.jclouds.rest.AuthorizationException: (root:rsa[fingerprint(0e:20:61:cc:e2:f9:af:e7:ac:a4:d8:5c:37:e8:3d:c5),sha1(c1:e5:62:7c:67:c5:c0:72:fe:91:4a:48:18:a4:00:00:58:ed:0f:fe)]@134.158.246.65:22) (root:rsa[fingerprint(0e:20:61:cc:e2:f9:af:e7:ac:a4:d8:5c:37:e8:3d:c5),sha1(c1:e5:62:7c:67:c5:c0:72:fe:91:4a:48:18:a4:00:00:58:ed:0f:fe)]@134.158.246.65:22) error acquiring {hostAndPort=134.158.246.65:22, loginUser=root, ssh=null, connectTimeout=60000, sessionTimeout=60000} (out of retries - max 7): Exhausted available authentication methods
at org.jclouds.sshj.SshjSshClient.propagate(SshjSshClient.java:380)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:201)
at org.jclouds.sshj.SshjSshClient.connect(SshjSshClient.java:221)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.call(RunScriptOnNodeAsInitScriptUsingSsh.java:76)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:125)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.apply(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:146)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.apply(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:53)
There is a class named:
org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSshAndBlockUntilComplete.java
which do not have any timeouts. Something in the SlaveTemplate should be parameterized for this class to be instanciated instead of
org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.java
?
- Status changed from Assigned to Closed
SL5 not supported anymore
Also available in: Atom
PDF
Updated by Brétel Foudil 
Updated by