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

Task log viewer for consul-connect enabled job switches erroneously #8222

Closed
djmarcin opened this issue Jun 19, 2020 · 4 comments
Closed

Task log viewer for consul-connect enabled job switches erroneously #8222

djmarcin opened this issue Jun 19, 2020 · 4 comments

Comments

@djmarcin
Copy link

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

Nomad v0.11.1 (b434570)

Operating system and Environment details

Ubuntu 20.04

Issue

When viewing a consul-connect enabled job, clicking into the task logs for the job will inexplicably switch to the consul-connect sidecar's logs after a period of about 10-20 seconds.

Reproduction steps

This seems to happen every almost every time for me.

  1. Create a consul-connect enabled job
  2. Click into the actual task for the job and navigate to the logs for the task
  3. Click stderr logs
  4. Wait 10-20s, the logs window will refresh to the consul-connect sidecar's logs.

Job file (if appropriate)

Nomad Client logs (if appropriate)

Nomad Server logs (if appropriate)

@spuder
Copy link
Contributor

spuder commented Jun 21, 2020

I am also seeing this issue. Has been a problem since 0.10.x and persists on 0.11.x

@betaboon
Copy link

this happens to me as well. but with a somewhat broader scope:

  • happens without consul-connect being enabled
  • happens on overview-tab as well as logs-tab
  • happens as soon as i put multiple tasks in the same group
  • only happens when there is at least one task failing and being restarted

@DingoEatingFuzz
Copy link
Contributor

I believe this is a duplicate of #8545 and fixed with #8833 which released in 0.12.5.

Feel free to reopen if you think this is a distinct bug.

@github-actions
Copy link

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 Oct 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants