[Fujitsu] Redundant scsi records of fujitsu volumes

Bug #1966397 reported by zhaoleilc
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Incomplete
Low
Unassigned
Rocky
New
Low
Unassigned

Bug Description

Description
===========
There are some redundant scsi records of fujitsu volumes
which prevent from attaching another new fujitsu volume
with same lun id.

For example, some redundant scsi records of fujitsu volumes
are as follows.
root@test:~# lsscsi | grep FU | grep -
[1:0:15:4] disk FUJITSU ETERNUS_DXM 1070 -
[1:0:15:8] disk FUJITSU ETERNUS_DXM 1070 -
[1:0:17:4] disk FUJITSU ETERNUS_DXM 1070 -
[1:0:17:8] disk FUJITSU ETERNUS_DXM 1070 -
[1:0:19:4] disk FUJITSU ETERNUS_DXM 1070 -

However, the lun id 4 and 8 are not used in storage so that
another new volume with lun id 4 or 8 cannot be attached
to instances in this host. Therefore, in case new volumes
fail to be attahed, these redundant scsi records need be
cleaned first.

Environment
===========
1. The version of OpenStack is rocky.
2. The Model Name and Firmware version of storage is respectively
ET60ESLCU and V10L60-9002.
3. The operation system of host is as follows.
root@compute-001:~# hostnamectl
   Static hostname: compute-001
         Icon name: computer-server
           Chassis: server
        Machine ID: 1ba872e56e7147c8980b2c4c2f05443f
           Boot ID: 580acebf925e4efb908fa1a0598301ab
  Operating System: Ubuntu 18.04.6 LTS
            Kernel: Linux 5.10.83
      Architecture: x86-64

Revision history for this message
Sofia Enriquez (lsofia-enriquez) wrote :

Greetings zhaoleilc,
is this bug also in master?
Thanks in advance,
Sofia

summary: - Redundant scsi records of fujitsu volumes
+ [Fujitsu] Redundant scsi records of fujitsu volumes
Changed in cinder:
status: New → Incomplete
tags: added: drivers fujitsu
Revision history for this message
Gorka Eguileor (gorka) wrote :

I don't know if the transport protocol for those SCSI volumes is iSCSI or FCP, but those LUNs were most likely used in storage at some point.

If it's iSCSI they are most likely caused by race conditions between concurrent attach/detach operations. This has been greatly improved in cinder, os-brick, and nova and it should no longer be an issue.

Another possibility is that os-brick failed to detach those volumes and Nova ignored these errors leaving dangling devices which still appear in your system.

You should check your logs to see what really happened with the detach of those LUNs that no longer exist on your storage.

Changed in cinder:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.