MountVolume.SetUp failed for volume "oneagent-bin"

[kevin_ortiz]

Hi, i have this error in the installation of the agent on k8:

  Warning  FailedMount  100s (x15 over 16m)  kubelet            MountVolume.SetUp failed for volume "oneagent-bin" : kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name csi.oneagent.dynatrace.com not found in the list of registered CSI drivers

can anyone help me please?

[VenkataSainath]

@kevin_ortiz Can you please confirm which Dynatrace operator version your using?

I think there was bug in Dynatrace operator 1.2.0, If your using the same version you can update to 1.2.2

https://docs.dynatrace.com/docs/shortlink/release-notes-dto-fix-1-2-2

 

[kevin_ortiz]

Hi @VenkataSainath , i have the last version available 1.3.2, i put here the output of the operator:

[root@SRV-K8S-M2-PRE ~]# kubectl exec deploy/dynatrace-operator -n dynatrace-pre -- dynatrace-operator troubleshoot

{"level":"info","ts":"2024-11-26T21:49:12.090Z","logger":"version","msg":"dynatrace-operator","version":"v1.3.2","gitCommit":"11b12492182e1f5b896adb4e9feb070373b1865c","buildDate":"2024-10-24T11:00:21+00:00","goVersion":"go1.23.2","platform":"linux/amd64"}

{"level":"info","ts":"2024-11-26T21:49:12.090Z","msg":"logging level","logLevel":"info"}

[oneAgentAPM]   --- checking if OneAgentAPM object exists ...

[oneAgentAPM]    ✓  OneAgentAPM does not exist

[namespace ]    --- checking if namespace 'dynatrace-pre' exists ...

[namespace ]     ✓  using namespace 'dynatrace-pre'

[          ]    no Dynakube specified - checking all Dynakubes in namespace 'dynatrace-pre'

[crd       ]    --- checking if CRD for Dynakube exists ...

[crd       ]     ✓  CRD for Dynakube exists

[dynakube  ]    --- checking if 'dynatrace-pre:cluster-pre' Dynakube is configured correctly

[dynakube  ]        using 'dynatrace-pre:cluster-pre' Dynakube

[dynakube  ]        secret token 'apiToken' exists

[dynakube  ]        checking if token scopes are valid

[dynakube  ]        token scopes are valid

[dynakube  ]        checking if can pull latest agent version

[dynakube  ]        API token is valid, can pull latest agent version

[dynakube  ]        pull secret 'dynatrace-pre:cluster-pre-pull-secret' exists

[dynakube  ]        secret token '.dockerconfigjson' exists

[dynakube  ]     ✓  'dynatrace-pre:cluster-pre' Dynakube is valid

[dynakube.imagepull]    --- Verifying that OneAgent image jpg94247.live.dynatrace.com/linux/oneagent:1.303.50-raw can be pulled ...

[dynakube.imagepull]     ✓  OneAgent image jpg94247.live.dynatrace.com/linux/oneagent:1.303.50-raw can be successfully pulled

[dynakube.imagepull]    --- Verifying that OneAgentCodeModules (custom image) image  can be pulled ...

[dynakube.imagepull]        No OneAgentCodeModules (custom image) image configured

[dynakube.imagepull]    --- Verifying that ActiveGate image jpg94247.live.dynatrace.com/linux/activegate:1.303.18-raw can be pulled ...

[dynakube.imagepull]     ✓  ActiveGate image jpg94247.live.dynatrace.com/linux/activegate:1.303.18-raw can be successfully pulled

[dynakube.proxy]        --- Analyzing proxy settings ...

[dynakube.proxy]         ✓  No proxy settings found.

[Peter_Youssef]

Hi @kevin_ortiz 

First of all you have to determine the current K8s deployment, is it the accurate method as per Dynatrace best practices and the actual setup or Not:

PFA Dynatrace related resources for detailed level of troubleshooting:

• https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/how-it-works
•  https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/reference/security
• https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/installation/other/host-monitoring
• https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/installation/supported-technologies
• https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/installation/troubleshooting

Entry Point to K8s:

• https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s
• https://github.com/Dynatrace/dynatrace-operator/blob/main/README.md

The recommended approach:

• https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/installation/cloud-native-fullstack

Simply:

• If the CSI Driver has been installed with issues, you can uninstall and re-install it again as per the attached resources, it's easily configured on K8s.

Hoping it helps.

KR,

Peter

[Peter_Youssef]

Hello @kevin_ortiz 

• It's recommended to keep the monitoring components "Cluster Nodes, OneAgents, AGs, Operator" up to date.
• Ensuring the target technology is supported by Dynatrace and updated.
• Feel free to review the troubleshooting guide: https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/installation/troubleshooting/monitoring-tro...
• In such cases it's better to simulate the case entirely on development environment, uninstall the Operator and related components, remove all related directories from K8s && conduct a clean K8s integration it will succeed.

Regards,

Peter