Exec in to container (from UI) always goes to the last allocation

[idrennanvmware]

Nomad version

Nomad v0.11.3 (8918fc8)

Operating system and Environment details

PhotonOS3

Issue

When using the UI in Nomad 0.11.3, in a job with 3 groups (with a count of 3), when "exec" in to the container it always goes to the last one.

Reproduction steps

Create a job with a group with a count of > 1. Place a unique environment variable in each one via the job template. Use the UI to exec in to to the container - the variables are always the "last" one. See screenshots. Whats interesting is that the EXEC window used to show 3 options to log in (one for each instance of the group). Now it always shows 1, which I assume is the last one (see the nav bar on the final screenshot). Note I was on the client with the IP 192.168.50.92 but the exec took me to the container on 192.168.50.93

[rkettelerij]

Good catch. This is weird indeed. To clarify: It not only happens when you click the Exec button on the job page. It also happens when you select a concrete allocation (you're on the allocation page) and use the Exec button: you always end up in the last allocation, not the selected allocation.

[idrennanvmware]

@rkettelerij - I just checked and it seems to be the same regardless of which level I exec from

Job
Group
Task

all always go to the same container

[rkettelerij]

@idrennanvmware Indeed

[backspace]

Thanks for letting us know about this and the thorough report!

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.