#11619 The SSH key of humaton cause playbook non-idempotence
Closed: Fixed a year ago by humaton. Opened a year ago by praiskup.

Everytime I run the playbook, the add root keys for sysadmin-main and other allowed users task does two changes:

changed: [copr-be-dev.aws.fedoraproject.org] => (item=ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC2y1EU7Ix2yu5zvMdjKivSjeL5/wYV3tie8tyn0=)
changed: [copr-be-dev.aws.fedoraproject.org] => (item=ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC2y1EU7Ix2yu5zvMdjKivSjeL5/wYV3tie8tyn0= humaton@fedora)

@humaton could you please take a look at your SSH key config in FAS?


Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

a year ago

The same key was in there twice, once with a comment and once without. ;)

I deleted the one that had no comment. This should fix it. ;)

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

a year ago

I'm I still see the same problem right now actually. Reopening.

Metadata Update from @praiskup:
- Issue status updated to: Open (was: Closed)

a year ago

Yeah, I guess he re-added it?

@humaton can you delete one of the 2 key copies you have there that are the same except for comment?

I did not add any new keys for a while now. And the key was really there twice, it's removed now.

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog