update image sfx duo to automation_images#415

[timcoding1988]

Does this PR introduce a user-facing change?

None

[Luap99]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, timcoding1988

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:

• OWNERS [Luap99]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[TomSweeneyRedHat]

LGTM

[Luap99]

/lgtm

[Luap99]

/hold

Do not merge, I thought there were some infra problems as two rawhide tasks just were listed scheduled since yesterday but the GCE VMs showed them us running but someone it is stucked in a retry loop connecting to the google metaddata server?

Seeing stuff like this in a loop

[   30.076248] audit: type=1130 audit(1755771684.791:89): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=google-guest-agent comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
[   30.203906] audit: type=1130 audit(1755771684.919:90): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Aug 21 05:21:24 packer-68a5db67-9c23-20a8-9b7a-b470ef7254b8 google_guest_agent[748]: ERROR instance_setup.go:168 Failed to reach MDS after attempt to recover network configuration(all retries exhausted): exhausted all (100) retries, last error: request failed with status code: [-1], error: [error connecting to metadata server: Get "http://169.254.169.254/computeMetadata/v1/?alt=json&recursive=true&timeout_sec=60": dial tcp 169.254.169.254:80: connect: network is unreachable]
Aug 21 05:21:24 packer-68a5db67-9c23-20a8-9b7a-b470ef7254b8 systemd[1]: google-guest-agent.service: Main process exited, code=exited, status=1/FAILURE

I killed the VMs and rerun the tasks one passed the other one could the same error again. So something in the rawhide images triggers a flake during early cloud setup, we cannot merge this as I don't see this on other PRs so it is almost certainly a problem with the new rawhide image.