# MountVolume.SetUp failed for volume "oneagent-bin"

**URL:** <https://community.dynatrace.com/t/mountvolume-setup-failed-for-volume-oneagent-bin/49068>\
**Category:** Container platforms\
**Tags:** kubernetes\
**Created:** [November 26, 2024, 3:05pm UTC](https://community.dynatrace.com/t/mountvolume-setup-failed-for-volume-oneagent-bin/49068 "2024-11-26T15:05:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevin\_ortiz](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@kevin\_ortiz](https://community.dynatrace.com/u/kevin_ortiz)\
**Post date:** [November 26, 2024, 3:05pm UTC](https://community.dynatrace.com/t/mountvolume-setup-failed-for-volume-oneagent-bin/49068/1 "2024-11-26T15:05:13Z")

</div>

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

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

can anyone help me please?

---

<div class="post-metadata">

**Author:** ![Venkata\_Sainath\_Ghanachari](https://avatars.discourse-cdn.com/v4/letter/v/3ab097/32.png) [@Venkata\_Sainath\_Ghanachari](https://community.dynatrace.com/u/Venkata_Sainath_Ghanachari)\
**Post date:** [November 27, 2024, 6:40am UTC](https://community.dynatrace.com/t/mountvolume-setup-failed-for-volume-oneagent-bin/49068/2 "2024-11-27T06:40:51Z")

</div>

[@kevin\_ortiz](https://community.dynatrace.com/user/78207) 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

> **[Dynatrace Operator release notes](https://docs.dynatrace.com/docs/whats-new/dynatrace-operator)**
>
> Release notes for Dynatrace Operator

---

<div class="post-metadata">

**Author:** ![kevin\_ortiz](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@kevin\_ortiz](https://community.dynatrace.com/u/kevin_ortiz)\
**Post date:** [November 27, 2024, 9:08am UTC](https://community.dynatrace.com/t/mountvolume-setup-failed-for-volume-oneagent-bin/49068/3 "2024-11-27T09:08:17Z")

</div>

Hi&nbsp;[@VenkataSainath](https://community.dynatrace.com/user/41639)&nbsp;, 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] &nbsp; --- checking if OneAgentAPM object exists …

[oneAgentAPM] &nbsp; &nbsp;✓ &nbsp;OneAgentAPM does not exist

[namespace] &nbsp; &nbsp;--- checking if namespace ‘dynatrace-pre’ exists …

[namespace] &nbsp; &nbsp; ✓ &nbsp;using namespace ‘dynatrace-pre’

[&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;] &nbsp; &nbsp;no Dynakube specified - checking all Dynakubes in namespace ‘dynatrace-pre’

[crd &nbsp; &nbsp; &nbsp;] &nbsp; &nbsp;--- checking if CRD for Dynakube exists …

[crd &nbsp; &nbsp; &nbsp;] &nbsp; &nbsp; ✓ &nbsp;CRD for Dynakube exists

[dynakube &nbsp;] &nbsp; &nbsp;--- checking if ‘dynatrace-pre:cluster-pre’ Dynakube is configured correctly

[dynakube &nbsp;] &nbsp; &nbsp; &nbsp; &nbsp;using ‘dynatrace-pre:cluster-pre’ Dynakube

[dynakube &nbsp;] &nbsp; &nbsp; &nbsp; &nbsp;secret token ‘apiToken’ exists

[dynakube &nbsp;] &nbsp; &nbsp; &nbsp; &nbsp;checking if token scopes are valid

[dynakube &nbsp;] &nbsp; &nbsp; &nbsp; &nbsp;token scopes are valid

[dynakube &nbsp;] &nbsp; &nbsp; &nbsp; &nbsp;checking if can pull latest agent version

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

[dynakube &nbsp;] &nbsp; &nbsp; &nbsp; &nbsp;pull secret ‘dynatrace-pre:cluster-pre-pull-secret’ exists

[dynakube &nbsp;] &nbsp; &nbsp; &nbsp; &nbsp;secret token ‘.dockerconfigjson’ exists

[dynakube &nbsp;] &nbsp; &nbsp; ✓ &nbsp;‘dynatrace-pre:cluster-pre’ Dynakube is valid

[dynakube.imagepull] &nbsp; &nbsp;--- Verifying that OneAgent image [Login - Dynatrace](http://jpg94247.live.dynatrace.com/linux/oneagent:1.303.50-raw) can be pulled …

[dynakube.imagepull] &nbsp; &nbsp; ✓ &nbsp;OneAgent image [Login - Dynatrace](http://jpg94247.live.dynatrace.com/linux/oneagent:1.303.50-raw) can be successfully pulled

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

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

[dynakube.imagepull] &nbsp; &nbsp;--- Verifying that ActiveGate image [Login - Dynatrace](http://jpg94247.live.dynatrace.com/linux/activegate:1.303.18-raw) can be pulled …

[dynakube.imagepull] &nbsp; &nbsp; ✓ &nbsp;ActiveGate image [Login - Dynatrace](http://jpg94247.live.dynatrace.com/linux/activegate:1.303.18-raw) can be successfully pulled

[dynakube.proxy] &nbsp; &nbsp; &nbsp; &nbsp;--- Analyzing proxy settings …

[dynakube.proxy] &nbsp; &nbsp; &nbsp; &nbsp; ✓ &nbsp;No proxy settings found.

---

<div class="post-metadata">

**Author:** ![Peter\_Youssef](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/peter_youssef/32/14668_2.png) [@Peter\_Youssef](https://community.dynatrace.com/u/Peter_Youssef)\
**Post date:** [November 27, 2024, 7:26pm UTC](https://community.dynatrace.com/t/mountvolume-setup-failed-for-volume-oneagent-bin/49068/4 "2024-11-27T19:26:04Z")

</div>

Hi&nbsp;[@kevin\_ortiz](https://community.dynatrace.com/user/78207)

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:

- [How it works — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/how-it-works)
- [Dynatrace Operator security — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/reference/security)
- [Get started with host monitoring — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/installation/other/host-monitoring)
- [Supported distributions — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/installation/supported-technologies)
- [Troubleshooting — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/installation/troubleshooting)

**Entry Point to K8s:**

- [Set up Dynatrace on Kubernetes — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s)
- [dynatrace-operator/README.md at main · Dynatrace/dynatrace-operator · GitHub](https://github.com/Dynatrace/dynatrace-operator/blob/main/README.md)

**The recommended approach:**

- [Get started with Kubernetes platform monitoring + Full-Stack observability — Dynatrace Docs](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

---

<div class="post-metadata">

**Author:** ![Peter\_Youssef](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/peter_youssef/32/14668_2.png) [@Peter\_Youssef](https://community.dynatrace.com/u/Peter_Youssef)\
**Post date:** [November 27, 2024, 7:42pm UTC](https://community.dynatrace.com/t/mountvolume-setup-failed-for-volume-oneagent-bin/49068/5 "2024-11-27T19:42:48Z")

</div>

Hello&nbsp;[@kevin\_ortiz](https://community.dynatrace.com/user/78207)

- 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:&nbsp;[Monitoring issues troubleshooting — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/installation/troubleshooting/monitoring-troubleshooting)
- 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

---

<div class="post-metadata">

**Author:** ![mdruckhammer](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@mdruckhammer](https://community.dynatrace.com/u/mdruckhammer)\
**Post date:** [February 14, 2025, 12:12am UTC](https://community.dynatrace.com/t/mountvolume-setup-failed-for-volume-oneagent-bin/49068/6 "2025-02-14T00:12:24Z")

</div>

I’m not sure if this is your issue, but we also had this error when we switched from cloud-native full stack to application monitoring. The version we had specified for cloud-native was in the format \<major\>.\<minor\>.\<release\> but application monitoring was expecting&nbsp;\<major\>.\<minor\>.\<release\>.\<timestamp\>.
