Nomad UI Exec namespace issues
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
For reporting security vulnerabilities please refer to the website.
If you have a question, prepend your issue with [question] or preferably use the nomad mailing list.
If filing a bug please include the following:
Nomad version
Output from nomad version
0.12.5+ent
Operating system and Environment details
Debian 9.12
Issue
It looks like the Nomad UI does not support the exec UI for namespaced jobs.
When I browse to a job running in a namespace, then to a task or allocation for that job, clicking the 'Exec' button pops open a window saying "Not Found". Inspecting the JS console for this window, I see that it is attempting to fetch the job from the api, but without the namespace parameter. Note that if I use the exec button from the Job or task group UI, the namespace parameter is passed to the popup window and the exec UI works correctly
Reproduction steps
- Launch a namespaced job
- Browse to the allocation or task view for the job
- Use the UI to try to exec to it
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by opening a namespaced job's allocation or task view and using the Exec button. Inspect the popup's JavaScript console and API request, then verify that the namespace is included and the exec UI works for the namespaced job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100