#13047 Some maintainer test VMs aren't accepting non-root logins
Closed: Fixed by james. Opened by james.

Kevin said he'd seen someone mention this over the holiday, had a look yesterday and reran the groups/maintainer-test.yml playbook over all of them today.

  • ppc64le-test.fedorainfracloud.org: Dead? Ansible last spoke to it on 2025-11-21

  • aarch64-test01.fedorainfracloud.org: Root only.

  • f42-test.fedorainfracloud.org: Root only.
  • f43-test.fedorainfracloud.org: Root only.
  • rawhide-test.fedorainfracloud.org: Root only.

  • aarch64-test02.fedorainfracloud.org: Working fine.

  • el9-test.fedorainfracloud.org: Working fine.
  • el10-test.fedorainfracloud.org: Working fine.
  • ppc64le-test02.fedorainfracloud.org: Working fine.

I assigned myself to look at it more, but probably won't get to look at it properly before Friday then just do it.

Also I did check the AWS security policy, and it looked fine. And the nothing jumped out at me from the logs, although all of the hosts get a lot of bad ssh connection attempts.

The ppc64le-test machine is in a lab in brno... perhaps @sharkcz could help us reset that one?

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

Okay, I've found two problems:

  1. sss_ssh_authorizedkeys james returns Error looking up public keys on aarch64-test01.fedorainfracloud.org and rawhide-test.fedorainfracloud.org
  2. Amazon images have /usr/lib/systemd/system/sshd.service.d/ec2-instance-connect.conf on f43 and f42 ... which overrides AuthorizedKeysCommand with /usr/bin/eic_run_authorized_keys and thus. sss_ssh_authorizedkeys never runs.

...the second we can fix/workaround in a few ways, and on f43 I've currently basically done:

echo '/usr/bin/sss_ssh_authorizedkeys "$@"' >> /usr/bin/eic_run_authorized_keys

...and that works again now.

Problem 1 was that the VPN certs had expired. Fixed that, so everything is better now ... should still do some longer term fix for the amazon eic_run_authorized_keys thing.

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

Metadata