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

Pod's logs following continually switching off #13235

Open
michalovjan opened this issue Oct 12, 2023 · 4 comments
Open

Pod's logs following continually switching off #13235

michalovjan opened this issue Oct 12, 2023 · 4 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@michalovjan
Copy link

michalovjan commented Oct 12, 2023

Hello Openshift console team! I've created a bug in follow feature for LogViewer component in Patternfly React but they suggested that the issue may be within the product. I'll copy+paste my report from patternfly/react-log-viewer#48.

Describe the problem
Hello, I am not a UI developer but I am encountering an issue with the LogViewer component in Openshift UI (logs of a pod), where the follow feature of LogViewer component is turning off after new lines of logs appear. Repeated resuming of following the log will resume the follow until a new lines appear when it turns off again.

Expected behavior
Turning on the feature of following logs should be kept on after new lines, otherwise the feature does not serve its purpose.

Is this issue blocking you?
It is not blocking me. The feature is very useful and manually scrolling down to follow logs is a big inconvenience.

Screenshots
output

What is your environment?

  • OS: macOS Sonoma 14.0 (23A344) (same behaviour on older major OS version)
  • Browser: Safari
  • Browser Version: 17.0 (19616.1.27.211.1)

What is your product and what release date are you targeting?
The product is Openshift UI.

Any other information?
I'd like to emphasize that the feature works correctly on Google Chrome.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 11, 2024
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 10, 2024
@michalovjan
Copy link
Author

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 12, 2024
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants