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
Doing a bit of issue cleanup on some old issues. It looks like the specific bug here was most likely fixed in #11110
But also, the design has changed slightly. Following a dispatch, the dispatched instance doesn't show up on the main jobs page (ex. /ui/jobs?namespace=*) but it does show up under Job Launches on the parent job's detail page (ex. /ui/jobs/example@default):
From there you can click thru to the individual dispatched instance (ex /ui/jobs/example%2Fdispatch-1661185381-93c906b2@default)
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
1.1.2
Operating system and Environment details
Issue
While running a parametrized task the nomad UI cannot be accessed for the job details. Not found screen is returned
Reproduction steps
Expected Result
Job details is accessible and can track progress of task
Actual Result
Not Found error screen is returned
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: