You have been subscribed to a public bug:
I found we can not attach one volume to one instance(this instance is in
hyperV compute node).
Test Env:
Cinder using Storwizedriver, and nova compute node is hyperV env.
When I want to attach one available volume to an instance which in hyper
compute node, after ran "nova volume-attach" command, the volume status still
is available(available-> attaching->availble), and from hyper compute node, in
compute.log. I got the following error message:
2013-09-05 19:54:30.273 2204 AUDIT nova.compute.manager
[req-a62e1672-c825-488f-998f-c5c58c64ccde 427700be22794f588b97ff07854e2031
dd8f0667af5c44bab29899fb88adae96] [instance:
1b892ca0-3b5f-4792-a394-e9de661b429a] Attaching volume
a053f7f3-8ffd-4392-b278-3791c2cd29bd to /dev/sdb
2013-09-05 19:54:30.305 2204 INFO nova.virt.hyperv.basevolumeutils
[req-a62e1672-c825-488f-998f-c5c58c64ccde 427700be22794f588b97ff07854e2031
dd8f0667af5c44bab29899fb88adae96] The ISCSI initiator name can't be found.
Choosing the default one
2013-09-05 19:54:30.336 2204 INFO urllib3.connectionpool [-] Starting new HTTP
connection (1): 9.123.137.71
2013-09-05 19:54:31.618 2204 ERROR nova.virt.hyperv.volumeops
[req-a62e1672-c825-488f-998f-c5c58c64ccde 427700be22794f588b97ff07854e2031
dd8f0667af5c44bab29899fb88adae96] Attach volume failed: <x_wmi: Unexpected COM
Error (-2147352567, 'Exception occurred.', (0, u'SWbemObjectEx', u'Generic
failure ', None, 0, -2147217407), None)>
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops Traceback (most
recent call last):
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops File
"C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V
Agent\Python27\lib\site-packages\nova\virt\hyperv\volumeops.py", line 113, in
attach_volume
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops
self._login_storage_target(connection_info)
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops File
"C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V
Agent\Python27\lib\site-packages\nova\virt\hyperv\volumeops.py", line 100, in
_login_storage_target
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops target_portal)
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops File
"C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V
Agent\Python27\lib\site-packages\nova\virt\hyperv\volumeutilsv2.py", line 53,
in login_storage_target
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops
TargetPortalPortNumber=target_port)
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops File
"C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V
Agent\Python27\lib\site-packages\wmi.py", line 431, in __call__
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops
handle_com_error ()
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops File
"C:\Program Files (x86)\IBM\SmartCloud Entry\Hyper-V
Agent\Python27\lib\site-packages\wmi.py", line 241, in handle_com_error
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops raise klass
(com_error=err)
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops x_wmi: <x_wmi:
Unexpected COM Error (-2147352567, 'Exception occurred.', (0, u'SWbemObjectEx',
u'Generic failure ', None, 0, -2147217407), None)>
2013-09-05 19:54:31.618 2204 TRACE nova.virt.hyperv.volumeops
** Affects: nova
Importance: Medium
Status: Incomplete
** Tags: havana-backport-potential hyper-v
--
Cannot attach a volume to a Hyper-V Nova instance with a Storwize v7000 target
https://bugs.launchpad.net/bugs/1221525
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
