-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Alicloud: fix comparison failures for SecurityGroupRule and SSHKey #8028
Conversation
Hi @bittopaz. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@@ -68,13 +70,40 @@ func (s *SSHKey) Find(c *fi.Context) (*SSHKey, error) { | |||
Name: fi.String(k.KeyPairName), | |||
KeyPairFingerPrint: fi.String(k.KeyPairFingerPrint), | |||
} | |||
|
|||
// Avoid spurious changes | |||
if fi.StringValue(actual.KeyPairFingerPrint) == compactKeyFingerprint(fi.StringValue(s.KeyPairFingerPrint)) { |
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.
Usually a KeyFingerprint looks like: "a7:b1:3e:3d:84:24:a2:5a:91:5f:6f:e9:cf:dd:2b:6a".
For unknown reason, when creating new ssh key, it returns key print without ":", eg: "a7b13e3d8424a25a915f6fe9cfdd2b6a".
But in describe sshkey method, it returns normal KeyFingerprint. So I made this compactKeyFingerprint
function to do comparison.
/ok-to-test |
/retest |
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bittopaz, zetaab 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 |
@zetaab Thank you! |
This is part of #4127.