Obviously, I'm taking a little bit to come back around on some of these myself.
I thought I had written you a reply before, but I must have forgotten to hit "Post Comment"
The first 11 lines are the interesting part.
> Unable to discovered iSCSI target iqn.2010-10.org.openstack:volume-d0433ba1-d2c1-478c-96a1-b9074c57c62e from 192.168.125.27:3260. discover_st /usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/volumeops.py:111
Means that 192.168.125.27 canot reach iqn.2010-10.org.openstack:volume-d0433ba1-d2c1-478c-96a1-b9074c57c62e so the driver can't complete the action. To further diagnose this ... we need to figure out how to tell if that network segment really can be traversed or not.
Can you verify you can make the network traversal?
@sina-sa
Obviously, I'm taking a little bit to come back around on some of these myself.
I thought I had written you a reply before, but I must have forgotten to hit "Post Comment"
The first 11 lines are the interesting part.
> Unable to discovered iSCSI target iqn.2010- 10.org. openstack: volume- d0433ba1- d2c1-478c- 96a1-b9074c57c6 2e from 192.168. 125.27: 3260. discover_st /usr/lib/ python2. 7/dist- packages/ nova/virt/ vmwareapi/ volumeops. py:111
Means that 192.168.125.27 canot reach iqn.2010- 10.org. openstack: volume- d0433ba1- d2c1-478c- 96a1-b9074c57c6 2e so the driver can't complete the action. To further diagnose this ... we need to figure out how to tell if that network segment really can be traversed or not.
Can you verify you can make the network traversal?