I missed to verify the driver service before I launched the workload, because the driver showed ‘IsAlive’ state from the controller GUI view but in fact the driver service was not up. I also retried this scenario on another controller node and driver node, and got the same result. So I guess there is a bug on the driver node status detection.
I missed to verify the driver service before I launched the workload, because the driver showed ‘IsAlive’ state from the controller GUI view but in fact the driver service was not up. I also retried this scenario on another controller node and driver node, and got the same result. So I guess there is a bug on the driver node status detection.