-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.21
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The new aws-5 cluster_profile in CI jobs seems to have a bug in the ssh keys. While trying out this profile in MicroShift we are seeing this error (the keys are used to scp/ssh into aws ec2 instances): + 07:47:52.347245231 /bin/bash:141 scp -F /tmp/secret/.ssh/config ec2-user@18.237.212.130:/tmp/init_output.txt /logs/artifacts/init_ec2_output.txt Warning: Permanently added '18.237.212.130' (ED25519) to the list of known hosts. ec2-user@18.237.212.130: Permission denied (publickey,gssapi-keyex,gssapi-with-mic). After some investigation we checked that the ssh-publickey has a typo: + 07:44:40.113803618 /bin/bash:65 awk '{print $1}' + 07:44:40.113822689 /bin/bash:65 cat /var/run/secrets/ci.openshift.io/cluster-profile/ssh-publickey sh-rsa Whereas other profiles(aws through aws-4) show the correct format: + 07:44:28.182778339 /bin/bash:65 cat /var/run/secrets/ci.openshift.io/cluster-profile/ssh-publickey + 07:44:28.182809910 /bin/bash:65 awk '{print $1}' ssh-rsa
Version-Release number of selected component (if applicable):
4.21
How reproducible:
100%
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info: