Due to constant vib version conflicts, which I'm still investigating. I think we should add something similar to the below bash loop, which we will run at a given time (TBD) maybe per plan. 

Maybe we need to keep a single VIB in one datastore and the others a symlink. 

[root@ecoesxi05:~] for ds in $(ls -l /vmfs/volumes | grep " -> " | awk '{print $9}'); do VIB="/vmfs/volumes/$ds/vmkfstools-wrapper.vib"; [ -f "$VIB" ] && echo -n "$ds | $(stat -c %s "$VIB")
 bytes | " && esxcli software sources vib get -v "$VIB" | grep "Version:" | sed 's/^[[:space:]]*//'; done
eco-iscsi-ds1 | 5474 bytes | Version: 0.2.0
eco-iscsi-ds2 | 4350 bytes | Version: 0.1.2
eco-iscsi-ds3 | 6978 bytes | Version: 0.3.0
eco-iscsi-ds4-vmfs5 | 4200 bytes | Version: 0.1.2
 

The above for loop just exposes our situation, now I still didn't figreout or know how to detect which of these gets update/replaced (with an earlier vib)

None the less adding a similar capability may help catch/debug vib version conflicts before they happen. Or think of a mechanizem where if we update a VIB it can only grow and it injects the same version to all the datastores.