You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ nomad acl bootstrap
$ export NOMAD_TOKEN=<The Bootstrap Token>
$ nomad var put nomad/jobs/foobar foo=bar
$ nomad run foobar.nomad
$ # Wait until the job deploys successfully.
$ sed -i 's/job_version=0/job_version=1/g' foobar.nomad
$ nomad run foobar.nomad
$ # Wait until the job deploys successfully.
I was able to confirm this with the current HEAD of main and sudo nomad agent -dev -acl-enabled. With the new identity block feature we're shipping in Nomad 1.5.0, I was also able to confirm that the problem isn't that the workload identity is somehow being invalidated (which I didn't think was possible but wanted to make sure):
$ nomad alloc exec c96 env | grep NOMAD_TOKEN
NOMAD_TOKEN=<redacted>
$ NOMAD_TOKEN=<redacted> nomad var get nomad/jobs/foobar
Namespace = default
Path = nomad/jobs/foobar
Create Time = 2023-02-27T09:41:49-05:00
Check Index = 21
Items
foo = bar
I've double-checked this by running a job that instead of tail -f runs the following bash script:
If I tail the logs of the new allocation, it's still getting the variable even after promotion. That strongly suggests the problem is happening somewhere in the Nomad client, maybe in the template hook. I'm going to chat with some of my colleagues about where to look next and one of us will report back here.
Nomad version
Nomad v1.4.4 (7f29429)
Operating system and Environment details
Linux nomad-bug-16259 #36-Ubuntu SMP Mon Jan 23 21:04:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Issue
Screen.Recording.2023-02-25.at.22.29.40.mp4
Reproduction steps
nomad-server.hcl
:nomad-client.hcl
:foobar.nomad
:Other things to say
Key requirements for this bug to reproduce:
update.canary
must be greater than zero.The text was updated successfully, but these errors were encountered: