Bug 1030055 - LVM volume extend does not resize iSCSI LUN
Summary: LVM volume extend does not resize iSCSI LUN
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 4.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: 5.0 (RHEL 7)
Assignee: Jon Bernard
QA Contact: Dafna Ron
URL:
Whiteboard:
Depends On:
Blocks: 1111685 1111690
TreeView+ depends on / blocked
 
Reported: 2013-11-13 20:09 UTC by Eric Harney
Modified: 2016-04-26 19:11 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, resizing an existing volume did not automatically send a request to tgt to update the volume's exported LUN. As a result, the new size would not be displayed when the volume was attached to an instance. To address this, volume LUNs are now exported when the volumes are attached to an instance (instead of during volume creation). This will ensure that any changes to the volume's size (before being attached) will be visible.
Clone Of:
: 1111685 1111690 (view as bug list)
Environment:
Last Closed: 2014-07-08 15:30:25 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1248415 0 None None None Never
OpenStack gerrit 58599 0 None None None Never
OpenStack gerrit 69787 0 None None None Never
OpenStack gerrit 70291 0 None None None Never
Red Hat Product Errata RHEA-2014:0852 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement - Block Storage 2014-07-08 19:22:44 UTC

Description Eric Harney 2013-11-13 20:09:42 UTC 
Reported upstream:

LVM volume extend does not resize iSCSI LUN.  Reported against tgtadm, may affect lioadm as well.

Compare "tgt-admin --show" size listed to LV and Cinder volume size after an extend.
Comment 1 Ayal Baron 2013-12-01 10:19:05 UTC 
Do we allow 'live' extend? if so then it would also require refreshing the device on the compute node...
Comment 2 Jon Bernard 2013-12-02 17:14:20 UTC 
This is a great question and I do not have an answer off hand.  When the iSCSI target is updated on the host, if the guest must also refresh (or other action) to see the update then I suspect there is more work to do.  This might already be implemented.. I don't know yet.  I will test this and let you know.
Comment 9 Jon Bernard 2014-04-15 21:01:17 UTC 
I need to retest this with what's been commited upstream recently.  Before now, my initial patch caused some intermittent gate issues and upstream decided to take a different approach.  I am not yet clear on how far this effort has gotten, will report my findings.
Comment 10 Jon Bernard 2014-04-16 19:34:54 UTC 
Ok, so this change:

https://review.openstack.org/#/c/70291/

causes only attached volumes to be exported via TGT.  Since you cannot extend an attached volume, basically you cannot get into this situation any more.  Live volume extension is a feature being worked on currently.

I will try to backport this patch for A5.
Comment 12 Jon Bernard 2014-05-07 12:49:45 UTC 
Fix committed upstream, next 5.0 build should pick it up.
Comment 14 Sergey Gotliv 2014-06-10 14:05:12 UTC 
I am checking if this is part of the latest Cinder build...
Comment 15 Sergey Gotliv 2014-06-10 17:58:39 UTC 
Fixed in python-cinder-2014.1-4.el7ost.noarch
Comment 16 Yogev Rabl 2014-06-16 08:28:01 UTC 
verified in: 
python-cinder-2014.1-4.el7ost.noarch
python-cinderclient-1.0.8-1.el7ost.noarch
openstack-cinder-2014.1-4.el7ost.noarch

Please notice, there's no 'live' extend. The client requires to refresh it settings to see the new size of the LUN.
Comment 19 errata-xmlrpc 2014-07-08 15:30:25 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0852.html
Note You need to log in before you can comment on or make changes to this bug.