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
Hi @Great-Stone, would you be able to provide more details on your configuration and how to reproduce this? I have been unable to reproduce this locally on either 1.6.1 or 1.6.2-dev.
I ran a local Nomad agent using the dev mode with ACL's enabled and bootstrapped, and ran an example job. I then created an ACL policy using the specification you posted and created an ACL token linked to this policy. I took the created ACL token and used this within the Nomad UI to sign in. When navigating to the job task group page, the exec button is available and works as expected.
Closing this as per the resolution comment in #18381 and because there has been no updated comment here. If this is still an issue, please feel free to reopen or create a new issue.
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.
Nomad version
nomad 1.6.1
Operating system and Environment details
ubuntu 20.04
Issue
The alloc-exec was applied, but the button is disabled, which is how it appears. However, clicking it will execute the exec.
Reproduction steps
Expected Result
If alloc-exec is allowed, the UI will show it as enabled.
Actual Result
If alloc-exec is allowed, clicks and web UI are executed, although disabled in the UI
Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
The text was updated successfully, but these errors were encountered: