Description

There seems to be a strange side-effect upgrading our Flatcar based Packer images for AWS from 2605.12.0 to 2765.2.0

We have some rspec script which validates our final image but this now fails with the following error:

     ×  Command: `sudo systemd-analyze verify /usr/lib/systemd/system/coreos-metadata.service` exit_status is expected to eq 0
     
     expected: 0
          got: 1
     
     (compared using ==)

This is very strange as nothing seems to have really changed for the script /usr/lib/systemd/system/coreos-metadata.service between those 2 releases. Installing from ISO and checking the command by hand gives:

# systemd-analyze verify /usr/lib/systemd/system/coreos-metadata.service
/run/systemd/system/docker.socket:8: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly.
/usr/lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.
coreos-metadata.service: Command ln is not executable: No such file or directory

and return code is indeed 1 and not 0 as expected. Changing the line:

ExecStartPost=ln -fs /run/metadata/flatcar /run/metadata/coreos

into

ExecStartPost=/usr/bin/ln -fs /run/metadata/flatcar /run/metadata/coreos

seems to make the problem disapear, however as this line is exactly the same between the 2 releases
it should also have failed in 2605.12.0

Impact

Not able to validate our Packer images based on Flatcar anymore

Environment and steps to reproduce

See all above

Expected behavior

same behaviour expected between 2605.12.0 and 2765.2.0 (either both failed or both succeed depending on fullpath of ln command usage or not)

Additional information

None