Description of problem:
There are two workarounds exist for start VM with 3PAR-ISCSI managed storage domain disk :

1) Regular ISCSI domain uses an fqdn which clashes with the cinderlib domain, to workaround, you can move the regular ISCSI domains to maintenance
Using a DNS name for an ISCSI portal, while when we send the parameters to the driver we send the IP address itself (the driver, at least the 3PAR one, does not seem to accept anything other than IP). While this host was already connected to that portal using the DNS name (our "legacy" storage could also be using the same storage backend). 

iscsiadm -m node -T iqn.2000-05.com.3pardata:20210002ac021f6b -p 3par-iscsi-1.scl.lab.tlv.redhat.com:3260 -u
 
2)Disconnecting 3PAR of hosts from storage-
Disconnecting hosts from ISCSI and connecting them to MBD.

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.5.4-0.1.el7.noarch
vdsm-4.30.24-2.el7ev.x86_64
Cinderlib version :0.9.0

How reproducible:
100%

Steps to Reproduce:
1.Create a managed block storage domain from 3PAR-ISCSI
2.Create VM 
3.Create disk from the storage domain created in step1
4.Attach the disk to the VM
5. Start VM

Actual results:
There are two workarounds exists for start VM with 3PAR-ISCSI managed storage domain disk

Expected results:
Conducting start VM of 3PAR-ISCSI MBD will be done without workarounds

Additional info:
I know that workarounds need to be done in order to conduct start VM with 3PAR ISCSI disk. The purpose is to conduct start VM without these workarounds.