Bug 1649479 - [RFE] OVF_STORE last update not exposed in the UI
Summary: [RFE] OVF_STORE last update not exposed in the UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.4.5
: ---
Assignee: Tal Nisan
QA Contact: Shir Fishbain
URL:
Whiteboard:
Depends On:
Blocks: 902971 1417161 1717336
TreeView+ depends on / blocked
 
Reported: 2018-11-13 16:58 UTC by Andrea Perotti
Modified: 2023-10-06 17:59 UTC (History)
10 users (show)

Fixed In Version: ovirt-engine-4.4.4.7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1717336 (view as bug list)
Environment:
Last Closed: 2021-04-14 11:39:53 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Before_the_fix_attachment(4.4.5-0) (125.60 KB, image/png)
2021-03-16 15:03 UTC, Shir Fishbain
no flags Details
After_the_fix(4.4.5-9) (126.80 KB, image/png)
2021-03-16 15:07 UTC, Shir Fishbain
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:1169 0 None None None 2021-04-14 11:41:00 UTC
oVirt gerrit 99252 0 'None' MERGED core: Set OVF disk last modified date upon OVF update 2021-02-16 11:24:12 UTC
oVirt gerrit 99253 0 'None' MERGED webadmin: Show last modified date for disks in the disks tab 2021-02-16 11:24:12 UTC
oVirt gerrit 113205 0 master MERGED webadmin: add last modified column to disks subtab 2021-02-16 11:24:11 UTC

Description Andrea Perotti 2018-11-13 16:58:25 UTC
Description of problem:

For each the storage domain is reported the creation date of all the data disk and of ovf_stores, i.e. url:

https://$RHV_MANAGER/ovirt-engine/webadmin/?#storage-disks;name=$SD_NAME

Is it possible to add the 'last update" date/date for each of the elements above?

This is very useful in case of DR tests because it would allow end users to know if the OVF_STORE is in coherent with the all data written in it and that the execution of "Update OVFs" completed succesfully (since it's async)


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

How reproducible:
Always

Actual results:
End user is unable to know if changes to data/metadata happened on the storage domain have been correctly saved.

Expected results:
To have the possibility to view the status of the SD with report of the last update on the OVF_STORE

Comment 3 Sandro Bonazzola 2019-01-28 09:41:47 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.

Comment 11 Yosi Ben Shimon 2019-11-13 11:28:57 UTC
I've tested the z-stream cloned bug#1717336 and it didn't pass.
Therefore, I'm moving this bug to ASSIGNED as well.

Comment 14 Ahmad Khiet 2020-06-16 14:13:21 UTC
the fix has been pushed to https://bugzilla.redhat.com/show_bug.cgi?id=1830705

Comment 22 Evelina Shames 2021-01-28 13:57:34 UTC
There is still no 'last update' column in https://$RHV_MANAGER/ovirt-engine/webadmin/?#storage-disks;name=$SD_NAME 
Version: engine-4.4.5.2-0.1.el8ev

Comment 24 Shir Fishbain 2021-03-16 15:02:28 UTC
Verified! Screenshots before the fix and after the fix attached 

Versions:
ovirt-engine-4.4.5.9-0.1.el8ev.noarch
vdsm-4.40.50.8-1.el8ev.x86_64

Comment 25 Shir Fishbain 2021-03-16 15:03:44 UTC
Created attachment 1763679 [details]
Before_the_fix_attachment(4.4.5-0)

Comment 26 Shir Fishbain 2021-03-16 15:07:06 UTC
Created attachment 1763680 [details]
After_the_fix(4.4.5-9)

Comment 31 errata-xmlrpc 2021-04-14 11:39:53 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 (Moderate: RHV Manager (ovirt-engine) 4.4.z [ovirt-4.4.5] security, bug fix, enhancement), 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/RHSA-2021:1169


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