Bug 1741153 - [downstream clone - 4.3.6] a new size of the direct LUN not updated in Admin Portal
Summary: [downstream clone - 4.3.6] a new size of the direct LUN not updated in Admin ...
Keywords:
Status: CLOSED DUPLICATE of bug 1741155
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.2.7
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.3.6
: ---
Assignee: Fedor Gavrilov
QA Contact: Avihai
URL:
Whiteboard:
Depends On: 1651939
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-14 11:34 UTC by RHV bug bot
Modified: 2019-08-15 12:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1651939
Environment:
Last Closed: 2019-08-15 12:51:56 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description RHV bug bot 2019-08-14 11:34:22 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1651939 +++
======================================================================

Description of problem:
The direct LUN is extended on a storage device. Since the Bug 1155275 "[RFE][Cinder] - Online update LUN size to the Guest after LUN resize" 
(https://bugzilla.redhat.com/show_bug.cgi?id=1155275) is not implemented yet, there is a recommendation to put the VM down and start again to have a new size:
https://access.redhat.com/solutions/1230283
The new size is ok for VM and is seen on the hypervisor, multipathd shows the proper size as well, but still in the Admin Portal the LUN size is not updated. 


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

How reproducible:
always

Steps to Reproduce:
1. expand LUN on a storage device
2. put the Vm down and start again
3. check and confirm the size inside the VM, even some VG increase can be performed, check on hypervisor the LUN size in multipathd
4. check GUI and confirm it is not updated.

Actual results:
not updated in Admin Portal only

Expected results:
it is updated everywhere

Additional info:
The problems seems to be lack of action "refreshlun" 
I fixed the problem running REST API request:

curl --request POST  --header "Accept: application/xml" --header "Host: ${FQDN}" --header "Authorization: Bearer  ${TOKEN}"  --cacert /etc/pki/ovirt-engine/apache-ca.pem https://${FQDN}:443/ovirt-engine/api/disks/${LUNID}/refreshlun --header "Content-Type: application/xml" --data "<action><host id='${HOSTID}'/></action>"

(Originally by Olimp Bockowski)

Comment 1 RHV bug bot 2019-08-14 11:34:24 UTC
Hi Olimp,
In that case I think the right way is to update the docs with the last step you mentioned, isn't it?

(Originally by Tal Nisan)

Comment 8 RHV bug bot 2019-08-14 11:34:36 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

(Originally by Sandro Bonazzola)

Comment 10 RHV bug bot 2019-08-14 11:34:40 UTC
How about adding a button to UI "refresh lun" that will run this API command per user request?

(Originally by Marina Kalinin)

Comment 12 RHV bug bot 2019-08-14 11:34:44 UTC
Adding an easy way to refresh LUN size sounds like a good idea, something
like "Refresh Host Capabilities".

(Originally by Nir Soffer)


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