Unexpected Machine showing in Group

[scme0]

Severity

Sev-3-Low - Not Blocking

Version

2024.1.11885

Latest Version

I could reproduce the problem in the latest build

What happened?

The customer was using a script to get the hostname of a machine on a deployment, then looping through this and displaying the name pre-2024.1, and this was working correctly. Now since they've upgraded to 2024.1, an extra machine is being pushed into the group (Machines-1) causing errant data to be created. Tested this internally going from 2023.4 to 2024.1 on-prem and while I didn't get an actual value pushed into the hostname list I did get a blank entry, which I feel shouldn't be there.
User is using the following line: 'Set-OctopusVariable -name "MachineHostnames" -value #{Octopus.Machine.Hostname}' Customer has a workaround.

Before update:

After update:

Reproduction

Create a script step with this script:

Set-OctopusVariable -name "MachineHostnames" -value $OctopusParameters["Octopus.Machine.Hostname"]
Write-host "Host" $OctopusParameters["Octopus.Machine.Hostname"]

Then a second script step with this script:

#{each machine in Octopus.Action[Run a Script].Output}
Write-Host Host: #{machine.MachineHostnames}
#{/each}

Error and Stacktrace

No response

More Information

No response

Workaround

No response

[octoreleasebot]

Release Note: Fix issue where extra machines would appear in the Machine group on deployment steps

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2024.1	2024.1.12087
2024.2	2024.2.3101
2024.3+	all releases