Bug 1868114

My browser in different TZ, hence there is 3 hour different.

The Creation Date in the RHV-M GUI/Webadmin appears to be from when the image was created and not when the Active snapshot was created.

~~~
# /usr/share/ovirt-engine/dbscripts/engine-psql.sh -x -c "SELECT i.image_guid, i.image_group_id, i.vm_snapshot_id,  b.disk_alias, i.parentid, s.snapshot_id, s.description, s.snapshot_type, i.creation_date FROM images as i JOIN snapshots AS s ON (i.vm_snapshot_id = s.snapshot_id) LEFT JOIN vm_static AS v ON (s.vm_id = v.vm_guid) JOIN base_disks AS b ON (i.image_group_id = b.disk_id) WHERE v.vm_name = 'test' ORDER BY creation_date, description, disk_alias;"
-[ RECORD 1 ]--+-------------------------------------
image_guid     | 4f83f524-7707-4454-a401-aba9bac8cb05
image_group_id | 36ef8965-c8f1-4091-8ada-1471d61ed6ff
vm_snapshot_id | 0fb21491-43ea-4cfe-8a21-d94385b0f10e
disk_alias     | test_Disk1
parentid       | 00000000-0000-0000-0000-000000000000
snapshot_id    | 0fb21491-43ea-4cfe-8a21-d94385b0f10e
description    | test
snapshot_type  | REGULAR
creation_date  | 2020-08-07 13:53:56-04  <<======

-[ RECORD 2 ]--+-------------------------------------
image_guid     | 02895277-e47b-4513-9577-36c3b19f620a
image_group_id | 36ef8965-c8f1-4091-8ada-1471d61ed6ff
vm_snapshot_id | 746a0e86-f7e3-4d8f-8fc2-2542059b2aeb
disk_alias     | test_Disk1
parentid       | 4f83f524-7707-4454-a401-aba9bac8cb05
snapshot_id    | 746a0e86-f7e3-4d8f-8fc2-2542059b2aeb
description    | Active VM
snapshot_type  | ACTIVE
creation_date  | 2020-08-11 12:04:34-04
~~~

HI Bimal,
I checked in my environment, and I did not see this issue.

what I did is the following: 
1- under storage-> storage domains -> [select the storage domain the with the needed VM) -> Disk Snapshots 
 
2- in the database I did the following query (and replaced v.vm_name to the vm name) : 
SELECT i.image_guid, i.image_group_id, i.vm_snapshot_id,  b.disk_alias, i.parentid, s.snapshot_id, s.description, s.snapshot_type, i.creation_date FROM images as i JOIN snapshots AS s ON (i.vm_snapshot_id = s.snapshot_id) LEFT JOIN vm_static AS v ON (s.vm_id = v.vm_guid) JOIN base_disks AS b ON (i.image_group_id = b.disk_id) WHERE v.vm_name = 'test' ORDER BY creation_date, description, disk_alias;


comparing the results from 1 & 2, I see the same creation date and time. with no time gaps or time zones issue.

I recommend to check the system date time, ovirt date time, and if there's a settings for that in the database. I guess its a configuration issue, not code related issue.

I'm waiting for you response.

Hello Ahmad.

Let try this way.

From the RHV-M UI/Webadmin.
Compute -> Virtual Machine -> Select the VM.
Lower Pane, click on Snapshots.
Click on General (eye) icon to expand on the Snapshots.

The non Active VM snapshot will ahve a Date info.
Note this date/time.

Now, from the RHV-M UI/Webamdin
Compute ->  Storage Domain -> Select the Storage Domain.
Click on Disk Snapshots.
See the Creation Date on the snapshot that is attached.

The date/time from the Virtual Machine snapshot info and the Storage domain Disk snapshot is different.

Thanks
Bimal.

Hi Bimal, 

After follwoing the steps in Comment #3, I can see that the date time between sql/storage domain snapshots/vm snapshots does not match.
the root cause for this bug is that there's a mismatch in the date viewing in each snapshot.

for example in VM snapshots:
the Active Vm (Disk) does not show a date time.
the snapshot after, shows the date time of the active vm.
the next snapshot shows the date time of the previous snapshot.
and so on.

Thanks for the information, it helped a lot.

Hi Bimal,

After further debugging and investigating this bug, I though that there is a mismatch between date time rows at first because of what I saw.
then, I see that the dates are correct, see the Disks sub-tab on each snapshot and check if the dates are right.
the creation date of an image will be different from the snapshot creation date, because of the image is created first, until the response is back from vdsm, the snapshot creation date will be updated.
so its not a bug, you can close it if you see that's the case in your environment.

Verified with the following steps:

From Compute -> Virtual Machines -> vm_name > Snapshots > Expand the General tab:
~~~
ACTIVE 
Date - Current

s1
Date Dec 24, 2020, 8:49:59 AM
~~~


From Compute -> Storage Domain -> sd > Disk Snapshots:
~~~
s1
Creation Date Dec 24, 2020, 8:49:59 AM

Version: rhv-4.4.4-6

Ahmad, is that ok? Is there something else I need to check?

Hi Evelina, 
you need to check the snapshot creation date see https://imgur.com/a/Eq1phXh
this date will be also present in disks under Compute -> Virtual Machines -> vm_name > Snapshots

(In reply to Ahmad Khiet from comment #12)
> Hi Evelina, 
> you need to check the snapshot creation date see https://imgur.com/a/Eq1phXh
> this date will be also present in disks under Compute -> Virtual Machines ->
> vm_name > Snapshots

That's what I did :)
Checked both  Virtual Machines -> vm_name > Snapshots and Storage Domain -> sd > Disk Snapshots and the date it the same.
Just Asked if I didn't miss anything else.
Thanks.

Moving to Verified.

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 (Low: RHV-M(ovirt-engine) 4.4.z security, bug fix, enhancement update [ovirt-4.4.4]), 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:0381

Due to QE capacity, we are not going to cover this issue in our automation