yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #38695
[Bug 1488233] Re: FC with LUN ID >255 not recognized
Post-Kilo Cinder uses os-brick. Since this fix went in to os-brick and
was released with version 0.4.0, Cinder now should work as of the
requirements update to that library version in commit
e50576c2d495e6828f335029e713655c27a6fc5b.
** Changed in: cinder
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1488233
Title:
FC with LUN ID >255 not recognized
Status in Cinder:
Invalid
Status in Cinder kilo series:
Fix Committed
Status in OpenStack Compute (nova):
New
Status in OpenStack Compute (nova) kilo series:
New
Status in os-brick:
Fix Released
Bug description:
(s390 architecture/System z Series only) FC LUNs with LUN ID >255 are not recognized by neither Cinder nor Nova when trying to attach the volume.
The issue is that Fibre-Channel volumes need to be added using the unit_add command with a properly formatted LUN string.
The string is set correctly for LUNs <=0xff. But not for LUN IDs within the range 0xff and 0xffff.
Due to this the volumes do not get properly added to the hypervisor configuration and the hypervisor does not find them.
Note: The change for Liberty os-brick is ready. I would also like to
patch it back to Kilo. Since os-brick has been integrated with
Liberty, but was separate before, I need to release a patch for Nova,
Cinder, and os-brick. Unfortunately there is no option on this page to
nominate the patch for Kilo. Can somebody help? Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1488233/+subscriptions