Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1026868 - Direct LUN is not being updated after resizing
Summary: Direct LUN is not being updated after resizing
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: All
OS: Linux
Target Milestone: ---
: 3.4.0
Assignee: Daniel Erez
QA Contact: Leonid Natapov
Whiteboard: storage
Depends On:
Blocks: rhev3.4beta 1142926
TreeView+ depends on / blocked
Reported: 2013-11-05 14:50 UTC by Pavel Zhukov
Modified: 2018-12-05 16:32 UTC (History)
15 users (show)

Fixed In Version: ovirt-engine-3.4.0_av2
Doc Type: Bug Fix
Doc Text:
Previously, changes made to the size of a direct LUN were recognized and implemented by VDSM, but not displayed in the web interface or the database. Now, with new tracking values in disk stats for direct LUN disks, the new size displays correctly in the web interface and the database.
Clone Of:
Last Closed: 2014-06-09 15:01:00 UTC
oVirt Team: Storage
Target Upstream Version:

Attachments (Terms of Use)
engine.log (deleted)
2013-11-05 14:51 UTC, Pavel Zhukov
no flags Details
vdsm.log 3.3 (deleted)
2013-11-05 14:54 UTC, Pavel Zhukov
no flags Details
device list (deleted)
2013-11-05 14:56 UTC, Pavel Zhukov
no flags Details

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0506 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Virtualization Manager 3.4.0 update 2014-06-09 18:55:38 UTC
oVirt gerrit 22978 None None None Never
oVirt gerrit 24235 None None None Never
oVirt gerrit 24527 None None None Never
oVirt gerrit 24689 None None None Never

Description Pavel Zhukov 2013-11-05 14:50:58 UTC
Description of problem:
Direct LUN size is not being updated even if vdsm and qemu can see new size.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Attach direct LUN to the VM
2. Resize backend device
3. (iscsi) rescan the sessions iscsiadm -m session -R
4. Check if VM can see new size
5. Optional: Stop VM
6. Deactivate LUN and activate it again

Actual results:
Old size is in  UI and DB. vdsClient returns new capacity. 

Expected results:
New size should be displayed and DB should be updated. 

Additional info:

Comment 1 Pavel Zhukov 2013-11-05 14:51:59 UTC
Created attachment 819808 [details]

Comment 2 Pavel Zhukov 2013-11-05 14:54:34 UTC
Created attachment 819810 [details]
vdsm.log 3.3

Comment 3 Pavel Zhukov 2013-11-05 14:56:44 UTC
Created attachment 819812 [details]
device list

Comment 6 Ayal Baron 2014-01-29 13:30:29 UTC
This was solved in 3.4

Comment 7 Aharon Canan 2014-01-29 13:47:09 UTC
so why not move it to "ON_QA" for verification in 3.4?

Comment 8 Daniel Erez 2014-01-29 14:31:58 UTC
The hasn't been resolved yet. Moving to ASSIGNED.

Comment 11 Leonid Natapov 2014-03-10 11:45:44 UTC
3.4.0-0.3.master.el6ev. We now display new size correctly in UI. VM operational.

Comment 12 errata-xmlrpc 2014-06-09 15:01:00 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.

Note You need to log in before you can comment on or make changes to this bug.