<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Application pods can't start post injection with &amp;quot;MountVolume.SetUp failed ...&amp;quot; error in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/Application-pods-can-t-start-post-injection-with-quot/ta-p/273048</link>
    <description>&lt;H2&gt;Self Service Summary&lt;/H2&gt;
&lt;P&gt;You want to monitor your application pods, but the pods fail to start after Oneagent initContainer injection. The pod's events show the following error message:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;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&lt;/LI-CODE&gt;
&lt;H2&gt;Solution&lt;/H2&gt;
&lt;OL dir="auto"&gt;
&lt;LI&gt;Ensure the CSI daemon set can schedule a CSI pod on all K8s cluster nodes where monitored applications are running. For example, if there are 5 cluster nodes, then it is required to have 5 CSI-driver pods, one pod per node.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Verify if the new cluster nodes don't have any custom taints. If there are, please tolerate the csi-driver pod against those custom taints in the csi-driver (operator) manifest (yaml) file. Check &lt;A href="https://community.dynatrace.com/t5/Troubleshooting/Dynatrace-Operator-Having-a-different-number-of-OA-CSI-pods-than/ta-p/262171" target="_self"&gt;this&lt;/A&gt; post for more details.&lt;/LI&gt;
&lt;/OL&gt;</description>
    <pubDate>Thu, 18 Sep 2025 09:59:29 GMT</pubDate>
    <dc:creator>shahinm</dc:creator>
    <dc:date>2025-09-18T09:59:29Z</dc:date>
    <item>
      <title>Application pods can't start post injection with "MountVolume.SetUp failed ..." error</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Application-pods-can-t-start-post-injection-with-quot/ta-p/273048</link>
      <description>&lt;H2&gt;Self Service Summary&lt;/H2&gt;
&lt;P&gt;You want to monitor your application pods, but the pods fail to start after Oneagent initContainer injection. The pod's events show the following error message:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;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&lt;/LI-CODE&gt;
&lt;H2&gt;Solution&lt;/H2&gt;
&lt;OL dir="auto"&gt;
&lt;LI&gt;Ensure the CSI daemon set can schedule a CSI pod on all K8s cluster nodes where monitored applications are running. For example, if there are 5 cluster nodes, then it is required to have 5 CSI-driver pods, one pod per node.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Verify if the new cluster nodes don't have any custom taints. If there are, please tolerate the csi-driver pod against those custom taints in the csi-driver (operator) manifest (yaml) file. Check &lt;A href="https://community.dynatrace.com/t5/Troubleshooting/Dynatrace-Operator-Having-a-different-number-of-OA-CSI-pods-than/ta-p/262171" target="_self"&gt;this&lt;/A&gt; post for more details.&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Thu, 18 Sep 2025 09:59:29 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Application-pods-can-t-start-post-injection-with-quot/ta-p/273048</guid>
      <dc:creator>shahinm</dc:creator>
      <dc:date>2025-09-18T09:59:29Z</dc:date>
    </item>
  </channel>
</rss>

