Bug 1741155 - [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 ERRATA
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
: 4.3.6
Assignee: Fedor Gavrilov
QA Contact: Shir Fishbain
URL:
Whiteboard:
: 1741153 (view as bug list)
Depends On: 1651939
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-14 11:36 UTC by RHV bug bot
Modified: 2023-03-24 15:14 UTC (History)
8 users (show)

Fixed In Version: ovirt-engine-4.3.6.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1651939
Environment:
Last Closed: 2019-10-10 15:36:58 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3010 0 None None None 2019-10-10 15:37:11 UTC

Description RHV bug bot 2019-08-14 11:36:26 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:37:16 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:37:29 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:37:33 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:37:36 UTC
Adding an easy way to refresh LUN size sounds like a good idea, something
like "Refresh Host Capabilities".

(Originally by Nir Soffer)

Comment 13 Tal Nisan 2019-08-15 12:51:56 UTC
*** Bug 1741153 has been marked as a duplicate of this bug. ***

Comment 14 RHV bug bot 2019-08-15 14:05:07 UTC
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[No relevant external trackers attached]

For more info please contact: rhv-devops

Comment 15 Avihai 2019-08-18 11:01:19 UTC
Hi Fedor,

Please confirm that steps to verify are:

1. expand ISCSI/FC LUN on a storage device
2. put the Vm down and start again
3. check and confirm the size inside the VM changed, check on hypervisor the LUN size in multipathd changes in size to the new size.
4. check GUI and confirm it also updated.

Comment 17 RHV bug bot 2019-08-23 13:26:00 UTC
INFO: Bug status (ON_QA) wasn't changed but the folowing should be fixed:

[No relevant external trackers attached]

For more info please contact: rhv-devops

Comment 19 Shir Fishbain 2019-08-26 14:07:10 UTC
Verified  
The new size (2G) updated from 1G to 2G
sdcn                                                                                   69:176  0    2G  0 disk  
└─360002ac0000000000000085300021f6b                                                   253:46   0    2G  0 mpath 

vdsm-4.30.25-1.el7ev.x86_64
ovirt-engine-4.3.6.3-0.1.el7.noarch

Comment 20 RHV bug bot 2019-08-29 13:05:23 UTC
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[No relevant external trackers attached]

For more info please contact: rhv-devops

Comment 21 RHV bug bot 2019-09-05 13:28:32 UTC
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[No relevant external trackers attached]

For more info please contact: rhv-devops

Comment 22 RHV bug bot 2019-09-05 13:34:16 UTC
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[No relevant external trackers attached]

For more info please contact: rhv-devops

Comment 23 RHV bug bot 2019-09-25 08:46:52 UTC
INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:

[No relevant external trackers attached]

For more info please contact: rhv-devops

Comment 25 errata-xmlrpc 2019-10-10 15:36:58 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.

https://access.redhat.com/errata/RHEA-2019:3010


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