c9s: afterburn-sshkeys fails to start when installing an OKD cluster

[karmab]

When installing an OKD cluster (on kvm), the afterburn-sshkeys services fails to start with the following information

Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp afterburn[1033]: Error: failed to run
Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp afterburn[1033]: Caused by:
Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp afterburn[1033]:     0: writing ssh keys
Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp afterburn[1033]:     1: maximum number of retries (10) reached
Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp afterburn[1033]:     2: failed to fetch
Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp afterburn[1033]:     3: error sending request for url (http://169.254.169.254/latest/meta-data/public-keys)
Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp afterburn[1033]:     4: operation timed out
Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp systemd[1]: [email protected]: Main process exited, code=exited, status=1/FAILURE
Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp systemd[1]: [email protected]: Failed with result 'exit-code'.
Jul 20 12:13:29 okd-ctlplane-0.karmalabs.corp systemd[1]: Failed to start Afterburn (SSH Keys).

Note that the image used to initially boot the system was fedora-coreos-40.20240701.3.0-openstack.x86_64.qcow2 but there's no openstack deployment involved

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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-sigs/prow repository.