-
Notifications
You must be signed in to change notification settings - Fork 173
Revert "mantle: make kola use ecdsa SSH keys" #1767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "mantle: make kola use ecdsa SSH keys" #1767
Conversation
This reverts commit 5c036d1. That commit broke `kola` on AWS, because that platform only supports RSA keys.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say LGTM to unbreak releases.
The most likely fix would be finding out why the current code create rsa-sha1 keys (as mentioned in #1749 (comment)) to be able to keep RSA keys for AWS support. |
fun. |
Let's get this round of releases out and then we can re-attempt to solve this problem for f33. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dustymabe, lucab, travier The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
… f33 For F33 let's re-enable RSA-SHA1 keys for now so our kola tests will work. The plan is to only re-enable this briefly while we wait for an upstream feature [1] to be implemented. We had moved to an ecdsa key [2] but AWS doesn't support non RSA keys [3] so we reverted it for now in [4]. [1] golang/go#37278 (comment) [2] coreos/coreos-assembler#1749 [3] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html#how-to-generate-your-own-key-and-import-it-to-aws [4] coreos/coreos-assembler#1767
… f33 For F33 let's re-enable RSA-SHA1 keys for now so our kola tests will work. The plan is to only re-enable this briefly while we wait for an upstream feature [1] to be implemented. We had moved to an ecdsa key [2] but AWS doesn't support non RSA keys [3] so we reverted it for now in [4]. [1] golang/go#37278 (comment) [2] coreos/coreos-assembler#1749 [3] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html#how-to-generate-your-own-key-and-import-it-to-aws [4] coreos/coreos-assembler#1767
… f33 For F33 let's re-enable RSA-SHA1 keys for now so our kola tests will work. The plan is to only re-enable this briefly while we wait for an upstream feature [1] to be implemented. We had moved to an ecdsa key [2] but AWS doesn't support non RSA keys [3] so we reverted it for now in [4]. [1] golang/go#37278 (comment) [2] coreos/coreos-assembler#1749 [3] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html#how-to-generate-your-own-key-and-import-it-to-aws [4] coreos/coreos-assembler#1767
This reverts commit 5c036d1.
That commit broke
kola
on AWS, because that platform only supportsRSA keys.
Ref: #1749 (comment)
/cc @dustymabe @jlebon