Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UI] Don't show placement failures in UI if there currently aren't any #3828

Closed
rkettelerij opened this issue Feb 2, 2018 · 2 comments
Closed
Labels

Comments

@rkettelerij
Copy link
Contributor

Nomad version

Nomad v0.7.1

Issue

Once a placement failure has occurred the 'placement failure error' will always stay visible in the UI, regardless if subsequent runs of that job succeed. Expected behaviour: The placement failure error should only be visible if a job is currently in a failed stage.

screen shot 2018-02-02 at 08 36 43

Reproduction steps

  • Start with a clean UI (e.g. purge all existing jobs nomad stop -purge myjob)
  • Deploy a job and cause a placement issue
  • Verify the placement issue is visible in the UI
  • Fix the placement issue, for example by adjusting the job and rerunning it
  • Expected behaviour: the previous placement failure isn't visible in the UI
  • Actual behaviour: the placement failure is still there.
@DingoEatingFuzz
Copy link
Contributor

Thanks for filing this @rkettelerij! It's fixed in #3956 and will be released in 0.8.0.

@github-actions
Copy link

github-actions bot commented Dec 3, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants