OneAgent pod won't even attempt to start. Doesn't show any error

[NavenduGupta]

I'm running Minikube on WSL on a windows laptop. I used to get CrashLoopBackOff error when OneAgent pod was getting started. 
I removed "tolerations" and logMonitoring from the dynakube.yaml. It works fine on one laptop but not on other. 
On the second laptop, it won't even attempt to start the oneAgent pod. ActiveGate pod is working fine and shows up in the deployment status in the environment. I created support-archive also and doesn't see any error. 

How do I debug this? where do I look? As OneAgent pod is not even there, I can't even look for logs.
One thing I noticed is that  /var/lib/docker/volumes/minikube/_data/lib/kubelet/plugins/csi.oneagent.dynatrace.com/data doesn't have _dynakube directory created. 

I remember from pas experience that when oneAgent start, it creates "/var/lib/docker/volumes/minikube/_data/lib/kubelet/plugins/csi.oneagent.dynatrace.com/data/_dynakube/<cluster-name>/osagent directory.

Has anybody else faced same/similar issue? Any insight will be greatly appreciated!!

[p_devulapalli]

@NavenduGupta Do you see anything in the Dynatrace operator logs?

kubectl -n dynatrace logs -f deployment/dynatrace-operator

[NavenduGupta]

no errors... bunch of info messages...

717 {"level":"info","ts":"2025-07-18T06:13:42.554Z","logger":"dynakube","msg":"reconciling DynaKube finished, no dynakub e available","namespace":"dynatrace","name":"<cluster-name>","result":"empty"}
718 {"level":"info","ts":"2025-07-18T06:13:42.554Z","logger":"dynakube","msg":"reconciling DynaKube","namespace":"dynatr ace","name":"<cluster-name>"}
719 {"level":"info","ts":"2025-07-18T06:13:42.581Z","logger":"dynakube","msg":"reconciling DynaKube finished, no dynakub e available","namespace":"dynatrace","name":"<cluster-name>","result":"empty"}
720 {"level":"info","ts":"2025-07-18T06:32:12.669Z","logger":"dynakube","msg":"reconciling DynaKube","namespace":"dynatr ace","name":"<cluster-name>"}
721 {"level":"info","ts":"2025-07-18T06:32:12.678Z","logger":"dynakube","msg":"reconciling DynaKube finished, no dynakub e available","namespace":"dynatrace","name":"<cluster-name>","result":"empty"}

[NavenduGupta]

here is some interesting messages in operator log... don't know what to infer.......

705 {"level":"info","ts":"2025-07-18T06:02:12.666Z","logger":"dynakube","msg":"start reconciling OneAgent"}
706 {"level":"info","ts":"2025-07-18T06:02:12.666Z","logger":"dynakube-oneagent","msg":"reconciling OneAgent"}
707 {"level":"info","ts":"2025-07-18T06:02:12.666Z","logger":"dynakube-version","msg":"skipping version status update fo r disabled section","updater":"oneagent"}
708 {"level":"info","ts":"2025-07-18T06:02:12.666Z","logger":"dynakube-oneagent","msg":"removing OneAgent daemonSet"}
7

[p_devulapalli]

@NavenduGupta Cant really say much from these logs but the below line points to removing OneAgent daemonSet which could be the reason why you don't see the OneAgent running .

Just to be sure, can you check if you have enough space on the volume ?

708 {"level":"info","ts":"2025-07-18T06:02:12.666Z","logger":"dynakube-oneagent","msg":"removing OneAgent daemonSet"}

[NavenduGupta]

@p_devulapalli I allocated 4GB to oneagent and 16 GB to Minikube...

Now I'm getting CrashLoopBackOff error for Oneagent. I have been getting this error for past 2 days... 

[NavenduGupta]

forgot to tag you @p_devulapalli in above responses...