Maybe I misunderstood what this feature does; I added it to the deployment yaml. should I have run dellctl install powerstore validate-connectivity after doing the deployment?
Thank you for your question, and for bringing this to our attention. We truly appreciate the opportunity to assist.
The validate‑connectivity process ensures that each cluster node maintains a healthy data‑path connection to the storage array. The specific validation steps vary by protocol.
For Fibre Channel, the system compares the initiators registered on the array with the initiator values reported on each cluster node under /sys/class/fc_host/*/port_name. A successful match confirms proper connectivity. If no match is found, the driver installation is stopped to prevent potential configuration issues.
If you'd like assistance reviewing the output, you can safely sanitize any sensitive information and share the dellctl results in your post. Below is an example, with full FC initiator names removed for security. The values on the left reflect what dellctl detected on the host, and the values on the right show the corresponding initiators detected on the array.
+ for INIT in $FC_LIST
+ '[' 21:00:... = 10:00:... ']'
+ for INIT in $FC_LIST
+ '[' 21:00:... = 10:00:... ']'
+ for INIT in $FC_LIST
+ '[' 21:00:... = 10:00:... ']'
+ for INIT in $FC_LIST
+ '[' 21:00:... = 10:00:... ']'
+ '[' -z '' ']'
+ echo 'No matching FC initiators found on this host'
Okay. I would recommend against users using the validate-connectivity: true option during dellctl install powerstore procedure. (automated install)
the validate-connectivity option is documented as: Run a DaemonSet on all nodes to verify connectivity to storage systems.
however, as described above by @tyea1 , what it does is check the PowerStore host registrations are defined correctly with the worker node initiator records. The validate-connectivity dellctl install powerstore option does not check the data path. It checks that the host registration is configured properly, and the WWNs (or presumably IQNs, NWNs) match for each host.
When you install CSM (either manually, or using dellctl install powerstore), the proper procedure is not to have the storage admin create the host registrations manually. These will be created by the CSI driver node pods when they first come up and perform a health check (when the CSM software is deployed and starts up).
Using the validate-connectivity: true option during the install process, these host registrations on the PowerStore should not be there. And the automated installer will check for the connections and fail out.
Bottom line: at this time the validate-connectivity: true option is either broken or counter-productive, as the check is in the wrong place in the deploy procedure. I'd request that this is reviewed by the product and engineering team to update in a future release.
tyea1
1 Rookie
•
2 Posts
•
2 Points
0
0
Posted February 26th, 2026 14:30
@dan.cohen We are engaged on this issue and working towards a solution that does not require the array to have the host initiator information.