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

operator: Live tail of logs not working on OpenShift-based clusters #5743

Closed
xperimental opened this issue Apr 1, 2022 · 1 comment · Fixed by #6443, #6444 or #6445
Closed

operator: Live tail of logs not working on OpenShift-based clusters #5743

xperimental opened this issue Apr 1, 2022 · 1 comment · Fixed by #6443, #6444 or #6445
Labels
keepalive An issue or PR that will be kept alive and never marked as stale. sig/operator

Comments

@xperimental
Copy link
Collaborator

Describe the bug
The "live tailing" function of Loki works correctly on a LokiStack deployed on kind, but it does not work on a LokiStack deployed on OCP.

Grafana reports the following error:

Live tailing was stopped due to following error: undefined 

logcli reports this error:

Tailing logs failed: Error response from server:  (websocket: bad handshake) 

This seems to be related to the issue that the components have TLS enabled when deployed on OCP, while this is disabled in the "development" configuration.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy a LokiStack with operator feature flag --with-tls-service-monitors enabled (default on OpenShift clusters)
  2. Try to tail logs using one of the clients

Expected behavior
A live tail of the requested log query.

@stale
Copy link

stale bot commented May 1, 2022

Hi! This issue has been automatically marked as stale because it has not had any
activity in the past 30 days.

We use a stalebot among other tools to help manage the state of issues in this project.
A stalebot can be very useful in closing issues in a number of cases; the most common
is closing issues or PRs where the original reporter has not responded.

Stalebots are also emotionless and cruel and can close issues which are still very relevant.

If this issue is important to you, please add a comment to keep it open. More importantly, please add a thumbs-up to the original issue entry.

We regularly sort for closed issues which have a stale label sorted by thumbs up.

We may also:

  • Mark issues as revivable if we think it's a valid issue but isn't something we are likely
    to prioritize in the future (the issue will still remain closed).
  • Add a keepalive label to silence the stalebot if the issue is very common/popular/important.

We are doing our best to respond, organize, and prioritize all issues but it can be a challenging task,
our sincere apologies if you find yourself at the mercy of the stalebot.

@stale stale bot added the stale A stale issue or PR that will automatically be closed. label May 1, 2022
@periklis periklis added the keepalive An issue or PR that will be kept alive and never marked as stale. label May 2, 2022
@stale stale bot removed the stale A stale issue or PR that will automatically be closed. label May 2, 2022
@xperimental xperimental reopened this Jun 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keepalive An issue or PR that will be kept alive and never marked as stale. sig/operator
Projects
None yet
2 participants