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

dynatrace-oneagent-csi-driver #2053

Closed
shashank2300 opened this issue Aug 22, 2023 · 1 comment
Closed

dynatrace-oneagent-csi-driver #2053

shashank2300 opened this issue Aug 22, 2023 · 1 comment
Labels
support request request for further assistance with an issue

Comments

@shashank2300
Copy link

csi driver pods are crashing intermittently and containers restart many times. As mentioned in below events, Liveness probe fails in csi driver pods and the pod is going to CrashLoopBackoff state. This is observed in multiple clusters. After we restart these pods few times these are working fine. But this issue is seen very often.

 Warning  Unhealthy       93m (x8 over 94m)    kubelet            Liveness probe failed: Get "http://192.168.32.119:10090/livez": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Normal   Created         81m (x8 over 103m)   kubelet            Created container provisioner
  Normal   Pulling         76m (x11 over 106m)  kubelet            Pulling image "registry.connect.redhat.com/dynatrace/dynatrace-operator:v0.12.1"
  Warning  Unhealthy       41m (x58 over 94m)   kubelet            Liveness probe failed: Get "http://192.168.32.119:10080/livez": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy       11m (x4 over 52m)    kubelet            Liveness probe failed: Get "http://192.168.32.119:10090/livez": dial tcp 192.168.32.119:10090: connect: connection refused
  Warning  BackOff         65s (x401 over 93m)  kubelet            Back-off restarting failed container

Dynatrace Operator version used: 0.12.1

@chrismuellner chrismuellner added the support request request for further assistance with an issue label Aug 25, 2023
@chrismuellner
Copy link
Collaborator

Thank you for opening a Dynatrace Operator Issue. We've identified and tagged the issue as a "Support request".

Dynatrace responds to requests like these via Dynatrace ONE support rather than Github. This helps our team respond as quickly as possible using the support team's tools and procedures.

Thanks for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support request request for further assistance with an issue
Projects
None yet
Development

No branches or pull requests

2 participants