Here is a trace from an example with LVM where the system is already logged in to the portal:
2014-05-01 19:09:58.486 4684 DEBUG urllib3.connectionpool [-] "GET /v1/f4299bee568d4ef480d2cea7a79df2f9/volumes/0131ba29-6b35-46d0-af93-7101834ce2f6 HTTP/1.1" 200 579 _make_request C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\urllib3\connectionpool.py:295 2014-05-01 19:09:58.502 4684 DEBUG nova.volume.cinder [req-58a8b771-3b80-4d1e-b308-d7214bb1cab3 0d69a383e7bf4882b31c0f870b9bc289 f4299bee568d4ef480d2cea7a79df2f9] Cinderclient connection created using URL: http://10.90.2.4:8776/v1/f4299bee568d4ef480d2cea7a79df2f9 cinderclient C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\volume\cinder.py:94 2014-05-01 19:09:58.502 4684 INFO urllib3.connectionpool [-] Starting new HTTP connection (1): 10.90.2.4 2014-05-01 19:09:59.532 4684 DEBUG urllib3.connectionpool [-] "POST /v1/f4299bee568d4ef480d2cea7a79df2f9/volumes/0131ba29-6b35-46d0-af93-7101834ce2f6/action HTTP/1.1" 200 447 _make_request C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\urllib3\connectionpool.py:295 2014-05-01 19:09:59.532 4684 DEBUG nova.virt.hyperv.volumeops [req-58a8b771-3b80-4d1e-b308-d7214bb1cab3 0d69a383e7bf4882b31c0f870b9bc289 f4299bee568d4ef480d2cea7a79df2f9] Attach_volume: {u'driver_volume_type': u'iscsi', 'serial': u'0131ba29-6b35-46d0-af93-7101834ce2f6', u'data': {u'access_mode': u'rw', u'target_discovered': False, u'encrypted': False, u'qos_specs': None, u'target_iqn': u'iqn.2010-10.org.openstack:volume-0131ba29-6b35-46d0-af93-7101834ce2f6', u'target_portal': u'10.90.2.4:3260', u'volume_id': u'0131ba29-6b35-46d0-af93-7101834ce2f6', u'target_lun': 1, u'auth_password': u'TGd87wRi8LvYhxJ2G8Wb', u'auth_username': u'qbyfoMHCARBKxe9B54Pv', u'auth_method': u'CHAP'}} to instance-0000002f attach_volume C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\volumeops.py:152 2014-05-01 19:09:59.627 4684 WARNING nova.virt.hyperv.basevolumeutils [req-58a8b771-3b80-4d1e-b308-d7214bb1cab3 0d69a383e7bf4882b31c0f870b9bc289 f4299bee568d4ef480d2cea7a79df2f9] JSBRYANT initiator sessions is [] 2014-05-01 19:09:59.627 4684 DEBUG nova.virt.hyperv.volumeops [req-58a8b771-3b80-4d1e-b308-d7214bb1cab3 0d69a383e7bf4882b31c0f870b9bc289 f4299bee568d4ef480d2cea7a79df2f9] Logging in on storage target. Portal: 10.90.2.4:3260, IQN: iqn.2010-10.org.openstack:volume-0131ba29-6b35-46d0-af93-7101834ce2f6, LUN: 1 _login_storage_target C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\nova\virt\hyperv\volumeops.py:103 2014-05-01 19:10:05.970 4684 DEBUG oslo.messaging._drivers.amqpdriver [-] MSG_ID is 3bd9263b04674f70b86f64dda1baa015 _send C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V Agent\Python27\lib\site-packages\oslo\messaging\_drivers\amqpdriver.py:358
I have debug showing that the initiator_sessions does show a WMI object.
Continuing to investigate why that might be.
Here is a trace from an example with LVM where the system is already logged in to the portal:
2014-05-01 19:09:58.486 4684 DEBUG urllib3. connectionpool [-] "GET /v1/f4299bee568 d4ef480d2cea7a7 9df2f9/ volumes/ 0131ba29- 6b35-46d0- af93-7101834ce2 f6 HTTP/1.1" 200 579 _make_request C:\Program Files (x86)\IBM\ SmartCloud Entry\Hyper-V Agent\Python27\ lib\site- packages\ urllib3\ connectionpool. py:295 3b80-4d1e- b308-d7214bb1ca b3 0d69a383e7bf488 2b31c0f870b9bc2 89 f4299bee568d4ef 480d2cea7a79df2 f9] Cinderclient connection created using URL: http:// 10.90.2. 4:8776/ v1/f4299bee568d 4ef480d2cea7a79 df2f9 cinderclient C:\Program Files (x86)\IBM\ SmartCloud Entry\Hyper-V Agent\Python27\ lib\site- packages\ nova\volume\ cinder. py:94 connectionpool [-] Starting new HTTP connection (1): 10.90.2.4 connectionpool [-] "POST /v1/f4299bee568 d4ef480d2cea7a7 9df2f9/ volumes/ 0131ba29- 6b35-46d0- af93-7101834ce2 f6/action HTTP/1.1" 200 447 _make_request C:\Program Files (x86)\IBM\ SmartCloud Entry\Hyper-V Agent\Python27\ lib\site- packages\ urllib3\ connectionpool. py:295 hyperv. volumeops [req-58a8b771- 3b80-4d1e- b308-d7214bb1ca b3 0d69a383e7bf488 2b31c0f870b9bc2 89 f4299bee568d4ef 480d2cea7a79df2 f9] Attach_volume: {u'driver_ volume_ type': u'iscsi', 'serial': u'0131ba29- 6b35-46d0- af93-7101834ce2 f6', u'data': {u'access_mode': u'rw', u'target_ discovered' : False, u'encrypted': False, u'qos_specs': None, u'target_iqn': u'iqn.2010- 10.org. openstack: volume- 0131ba29- 6b35-46d0- af93-7101834ce2 f6', u'target_portal': u'10.90.2.4:3260', u'volume_id': u'0131ba29- 6b35-46d0- af93-7101834ce2 f6', u'target_lun': 1, u'auth_password': u'TGd87wRi8LvYh xJ2G8Wb' , u'auth_username': u'qbyfoMHCARBKx e9B54Pv' , u'auth_method': u'CHAP'}} to instance-0000002f attach_volume C:\Program Files (x86)\IBM\ SmartCloud Entry\Hyper-V Agent\Python27\ lib\site- packages\ nova\virt\ hyperv\ volumeops. py:152 hyperv. basevolumeutils [req-58a8b771- 3b80-4d1e- b308-d7214bb1ca b3 0d69a383e7bf488 2b31c0f870b9bc2 89 f4299bee568d4ef 480d2cea7a79df2 f9] JSBRYANT initiator sessions is [] hyperv. volumeops [req-58a8b771- 3b80-4d1e- b308-d7214bb1ca b3 0d69a383e7bf488 2b31c0f870b9bc2 89 f4299bee568d4ef 480d2cea7a79df2 f9] Logging in on storage target. Portal: 10.90.2.4:3260, IQN: iqn.2010- 10.org. openstack: volume- 0131ba29- 6b35-46d0- af93-7101834ce2 f6, LUN: 1 _login_ storage_ target C:\Program Files (x86)\IBM\ SmartCloud Entry\Hyper-V Agent\Python27\ lib\site- packages\ nova\virt\ hyperv\ volumeops. py:103 _drivers. amqpdriver [-] MSG_ID is 3bd9263b04674f7 0b86f64dda1baa0 15 _send C:\Program Files (x86)\IBM\ SmartCloud Entry\Hyper-V Agent\Python27\ lib\site- packages\ oslo\messaging\ _drivers\ amqpdriver. py:358
2014-05-01 19:09:58.502 4684 DEBUG nova.volume.cinder [req-58a8b771-
2014-05-01 19:09:58.502 4684 INFO urllib3.
2014-05-01 19:09:59.532 4684 DEBUG urllib3.
2014-05-01 19:09:59.532 4684 DEBUG nova.virt.
2014-05-01 19:09:59.627 4684 WARNING nova.virt.
2014-05-01 19:09:59.627 4684 DEBUG nova.virt.
2014-05-01 19:10:05.970 4684 DEBUG oslo.messaging.
I have debug showing that the initiator_sessions does show a WMI object.
Continuing to investigate why that might be.