Skip to main content
NetApp Knowledge Base

OpenStack: Attaching a second volume to the VM failed with the error Unable to find a Fibre Channel volume device

  1. Last updated
  2. Save as PDF
Views:
102
Visibility:
Public
Votes:
0
Category:
openstack
Specialty:
virt
Last Updated:

Applies to

  • OpenStack
  • Fibre Channel

Issue

The first volume attaches to the VM successfully. However, when attaching a second volume to the same VM, the storage maps a LUN to the compute node, but it gets unmapped within 10 seconds.

cinder-volume:

23 DEBUG cinder.volume.drivers.netapp.dataontap.block_base [req-20b6f8d2-2619-4381-8a5a-134b0505fc4c b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - - -] Mapped LUN volume-383016d9-265d-411f-a277-49f51f09d525 to the initiator(s) ['10:00:70:b7:e4:28:56:31', '10:00:70:b7:e4:28:56:30'] initialize_connection_fc /usr/lib/python3.9/site-packages/cinder/volume/drivers/netapp/dataontap/block_base.py:1005
23 DEBUG cinder.volume.drivers.netapp.dataontap.block_base [req-20b6f8d2-2619-4381-8a5a-134b0505fc4c b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - - -] Successfully fetched target details for LUN volume-383016d9-265d-411f-a277-49f51f09d525 and initiator(s) ['10:00:70:b7:e4:28:56:31', '10:00:70:b7:e4:28:56:30'] initialize_connection_fc /usr/lib/python3.9/site-packages/cinder/volume/drivers/netapp/dataontap/block_base.py:1012
23 DEBUG cinder.volume.manager [req-20b6f8d2-2619-4381-8a5a-134b0505fc4c b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - - -] Connection info returned from driver {'target_discovered': True, 'target_lun': 4, 'target_wwn': ['204dd039eac514a1', '2043d039eac514a1', '204ed039eac514a1', '2044d039eac514a1', '204fd039eac514a1', '2045d039eac514a1', '2050d039eac514a1', '2046d039eac514a1', '2051d039eac514a1', '2047d039eac514a1', '2052d039eac514a1', '2048d039eac514a1', '2053d039eac514a1', '2049d039eac514a1', '2054d039eac514a1', '204ad039eac514a1', '2055d039eac514a1', '204bd039eac514a1', '2056d039eac514a1', '204cd039eac514a1'], 'initiator_target_map': {'100070b7e4285631': ['204dd039eac514a1', '2043d039eac514a1', '204ed039eac514a1', '2044d039eac514a1', '204fd039eac514a1', '2045d039eac514a1', '2050d039eac514a1', '2046d039eac514a1', '2051d039eac514a1', '2047d039eac514a1', '2052d039eac514a1', '2048d039eac514a1', '2053d039eac514a1', '2049d039eac514a1', '2054d039eac514a1', '204ad039eac514a1', '2055d039eac514a1', '204bd039eac514a1', '2056d039eac514a1', '204cd039eac514a1'], '100070b7e4285630': ['204dd039eac514a1', '2043d039eac514a1', '204ed039eac514a1', '2044d039eac514a1', '204fd039eac514a1', '2045d039eac514a1', '2050d039eac514a1', '2046d039eac514a1', '2051d039eac514a1', '2047d039eac514a1', '2052d039eac514a1', '2048d039eac514a1', '2053d039eac514a1', '2049d039eac514a1', '2054d039eac514a1', '204ad039eac514a1', '2055d039eac514a1', '204bd039eac514a1', '2056d039eac514a1', '204cd039eac514a1']}, 'qos_specs': None, 'access_mode': 'rw', 'encrypted': False, 'cacheable': False, 'driver_volume_type': 'fibre_channel', 'attachment_id': '67e853b0-f3d2-462c-bf36-2f88f1b11852'} _connection_create /usr/lib/python3.9/site-packages/cinder/volume/manager.py:4694
2025-05-18 11:25:03.584 23 INFO cinder.volume.manager [req-20b6f8d2-2619-4381-8a5a-134b0505fc4c b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - - -] attachment_update completed successfully.

23 DEBUG cinder.volume.drivers.netapp.dataontap.block_base [req-42f4c571-6f34-4d05-aece-1db7c7cd5485 b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - - -] Unmapping LUN volume-383016d9-265d-411f-a277-49f51f09d525 from the initiators ['10:00:70:b7:e4:28:56:31', '10:00:70:b7:e4:28:56:30'] terminate_connection_fc /usr/lib/python3.9/site-packages/cinder/volume/drivers/netapp/dataontap/block_base.py:1049
23 INFO cinder.volume.manager [req-42f4c571-6f34-4d05-aece-1db7c7cd5485 b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - - -] Terminate volume connection completed successfully.
2025-05-18 11:25:13.786 23 DEBUG cinder.volume.manager [req-42f4c571-6f34-4d05-aece-1db7c7cd5485 b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - - -] Deleting attachment 67e853b0-f3d2-462c-bf36-2f88f1b11852. _do_attachment_delete /usr/lib/python3.9/site-packages/cinder/volume/manager.py:4843


nova-compute:

2025-05-18 11:25:02.357 2 INFO nova.compute.manager [req-e5418f44-a145-4015-9bd7-7be3e264f462 b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - default default] [instance: 65aba59b-44eb-4807-ac7b-a7b2945a17bc] Attaching volume 383016d9-265d-411f-a277-49f51f09d525 to /dev/vdc

2025-05-18 11:25:03.603 2 INFO os_brick.initiator.connectors.fibre_channel [-] Fibre Channel volume device not yet found. Will rescan & retry.  Try number: 0.
…………..
2025-05-18 11:25:11.606 2 INFO os_brick.initiator.connectors.fibre_channel [-] Fibre Channel volume device not yet found. Will rescan & retry.  Try number: 4.

2025-05-18 11:25:13.609 2 DEBUG os_brick.initiator.connectors.fibre_channel [-] Looking for Fibre Channel dev /dev/disk/by-path/pci-0000:98:00.0-fc-0x204cd039eac514a1-lun-4 _wait_for_device_discovery /usr/lib/python3.9/site-packages/os_brick/initiator/connectors/fibre_channel.py:222
2025-05-18 11:25:13.609 2 ERROR os_brick.initiator.connectors.fibre_channel [-] Fibre Channel volume device not found.
2025-05-18 11:25:13.609 2 ERROR oslo.service.loopingcall [-] Fixed interval looping call 'os_brick.initiator.connectors.fibre_channel.FibreChannelConnector.connect_volume.._wait_for_device_discovery' failed: os_brick.exception.NoFibreChannelVolumeDeviceFound: Unable to find a Fibre Channel volume device.
2025-05-18 11:25:13.609 2 ERROR oslo.service.loopingcall Traceback (most recent call last):
2025-05-18 11:25:13.609 2 ERROR oslo.service.loopingcall   File "/usr/lib/python3.9/site-packages/oslo_service/loopingcall.py", line 150, in _run_loop
2025-05-18 11:25:13.609 2 ERROR oslo.service.loopingcall     result = func(*self.args, **self.kw)
2025-05-18 11:25:13.609 2 ERROR oslo.service.loopingcall   File "/usr/lib/python3.9/site-packages/os_brick/initiator/connectors/fibre_channel.py", line 233, in _wait_for_device_discovery
2025-05-18 11:25:13.609 2 ERROR oslo.service.loopingcall     raise exception.NoFibreChannelVolumeDeviceFound()
2025-05-18 11:25:13.609 2 ERROR oslo.service.loopingcall os_brick.exception.NoFibreChannelVolumeDeviceFound: Unable to find a Fibre Channel volume device.
2025-05-18 11:25:13.609 2 ERROR oslo.service.loopingcall
2025-05-18 11:25:13.610 2 DEBUG os_brick.initiator.connectors.base [req-e5418f44-a145-4015-9bd7-7be3e264f462 b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - default default] Lock "connect_volume" "released" by "os_brick.initiator.connectors.fibre_channel.FibreChannelConnector.connect_volume" :: held 10.011s inner /usr/lib/python3.9/site-packages/os_brick/initiator/connectors/base.py:83
2025-05-18 11:25:13.610 2 DEBUG os_brick.initiator.connectors.fibre_channel [req-e5418f44-a145-4015-9bd7-7be3e264f462 b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - default default] <== connect_volume: exception (10012ms) NoFibreChannelVolumeDeviceFound('Unable to find a Fibre Channel volume device.') trace_logging_wrapper /usr/lib/python3.9/site-packages/os_brick/utils.py:176
2025-05-18 11:25:13.610 2 ERROR nova.virt.block_device [req-e5418f44-a145-4015-9bd7-7be3e264f462 b44211db8a4341b79d73619a3dcab2c6 9294dd1a171648b4b5d51185081cc3b6 - default default] [instance: 65aba59b-44eb-4807-ac7b-a7b2945a17bc] Driver failed to attach volume 383016d9-265d-411f-a277-49f51f09d525 at /dev/vdc: os_brick.exception.NoFibreChannelVolumeDeviceFound: Unable to find a Fibre Channel volume device.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.