The Generic Device Plugin (GDP) configuration parsing in MicroShift, specifically when evaluating the type field for paths (e.g., path.Type), does not properly handle values that do not exactly match DevicePathType ("Device") or MountPathType ("Mount"). This includes mis-cased values (e.g., "device", "mount") or arbitrary typos. Such unrecognized values cause the specific path configuration to be silently ignored, leading to unexpected behavior without any error or warning to the user

4.20

always

1. Install microshift 4.20 cluster
2. Now create a file on the host `echo "Hello, testing gdp" > /tmp/myconfig.txt
3. Now add below content into the microshift config.yaml and restart microshift
4. Now create a pod with the spec below

I see that file is not visible inside the container as the way type: mount was configured was incorrect, instead it should have been `type: Mount`

 If an unrecognized or invalid type value is provided, it should log an error or warning message, indicating that the configuration for that path could not be processed due to an invalid type
(or)
Potentially fall back to a default Type (e.g., DevicePathType) after logging a warning about the unrecognized input or normalize input 

https://redhat-internal.slack.com/archives/C03CJTNLKAT/p1752049186199299