-
Notifications
You must be signed in to change notification settings - Fork 2k
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] Logs from other tasks in same group interleaved in logs view #8545
Comments
I haven't yet tried to reproduce this bug. But if it's correct (I assume so) then it sounds like a serious regression. Especially because having multiple tasks per group is rather common in my experience. The 0.11.x line doesn't show this behaviour, of that I'm sure. /cc @backspace @DingoEatingFuzz |
I haven't tried to reproduce this yet either, but I'm also not sure how this could be a UI issue. I'm surprised by software every day, so I'm not saying it isn't a UI bug, but I'd be curious to see if anyone can reproduce it via the CLI or API. |
I guess "interleaved" was a not a great choice of words; the UI kind of "blinks" when it happens and there's only ever one tasks' is visible at any point in time. I have not confirmed the causality but it seems to mostly or only happen when tasks/containers restart or get rescheduled. I have not yet observed this in the cli, though I haven't had it open when it triggers in the UI. |
I was under the impression that logs would get mixed together, all of the time. Great to hear that's not the case. @Legogris Perhaps an animated gif that demonstrates the issue would help clarify things? |
So to my mild surprise, it was a UI bug. PR open: #8833 |
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. |
Nomad version
Nomad v0.12.1 (14a6893a250fc5f652eee4c7b52d8f95c3185aef)
Issue
When viewing the logs for a task, intermittently the logs will be replaced by those of a different task in the same group.
Reproduction steps
docker
. No specific configuration for logging in either client or job spec.The text was updated successfully, but these errors were encountered: