Broken github action for latest ?

[laluka]

Hello there,
I maintain the LaluBuntu linux distro (offensive work), and it's relying on packer & github actions for daily builds (docker mostly). We live on latest as it's a rolling distro, and this morning, things broke in the latest github action, any chance you could have a look ? :)
Cheers ! 🌹

Expected Behavior

packer version should work :)

Current Behavior

packer version doesn't work anymore :(

Steps to Reproduce

Simply add the packer setup workflow

[...]
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup `packer`
        uses: hashicorp/setup-packer@main
        id: setup
        env:
          PACKER_LOG: "0"
          PRODUCT_VERSION: latest

Environment

• Lalubuntu packer workflow: https://github.com/laluka/lalubuntu/blob/master/.github/workflows/packer.yml#L35
• Failing job logs: https://github.com/laluka/lalubuntu/actions/runs/10176077646/job/28146434543

Have a nice day ! 🌈

[ksatirli]

Thanks for reporting this, @laluka!

I tried to replicate this, because the error message is a bit confusing.

Here's my workflow output: https://github.com/ksatirli/packer-test/actions/runs/10179709241/job/28156033146

And here's the associated workflow: https://github.com/ksatirli/packer-test/blob/main/.github/workflows/packer-main.yml

I think the problem is that you're attempting to write to an out location that doesn't exist (as listed in your screenshot), but I'm unable to replicate this easily.

Can you provide more information?

[laluka]

Well, that's... Unexpected!
So, my report wasn't full, I thought the command failed as packer wasn't in the current PATH, but it actually is, the missing part was...

Now I wonder why github-action broke this behavior, as writing to stdout isn't too scary.. 🤷

It works on my end with a regular file, would you mind trying with /dev/stdout to see if this can still be reproduced ?

Thanks for the quick response, and have a nice day ! 🌹