Erroneous capacity due to residual fibre channel path

Bug #1908625 reported by zhaoleilc
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-brick
New
Low
Unassigned

Bug Description

Description
===========
There are some residual paths in /dev/disk/by-path directory
for fibre channel volume such as "/dev/disk/by-path/pci-0000
:3c:00.1-fc-0x56c92bfa002141e9-lun-3" where lun-3 is indicative
for the third volume on this node. However, the path is not a
valid path. And that leads to retrieve the same capacity as lun-3
instead of the real capacity when the other volume whose lun id
is 3 is attached to the host.

Steps to reproduce
==================
1. Assume that the node has a residual fibre channel path whose
capacity is 3G
2. Attach the other volume which has the same lun id to the instance
on the node and this volume is 5G
3. Inspect the capacity in the instance.

Expected result
===============
The new attached volume in the instance is 5G.

Actual result
=============
The capacity is 3G.

Environment
===========
the victoria branch of os-brick

Logs & Configs
==============
None

tags: added: capacity fc volume
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on os-brick (stable/victoria)

Change abandoned by "Rajat Dhasmana <email address hidden>" on branch: stable/victoria
Review: https://review.opendev.org/c/openstack/os-brick/+/767662
Reason: This patch should be proposed to master first and author hasn't responded to the review comments since 5+ months

Changed in os-brick:
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.