Bug 1926854

Summary: [RFE] Requesting an audit log entry be added in LSM flow to display the host on which the internal volumes are copied
Product: Red Hat Enterprise Virtualization Manager Reporter: Gordon Watson <gwatson>
Component: ovirt-engineAssignee: Ahmad Khiet <akhiet>
Status: CLOSED ERRATA QA Contact: sshmulev
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.3CC: akhiet, aoconnor, dfodor, eshenitz, jbreitwe, mkalinin, sfishbai, sfroemer, tnisan
Target Milestone: ovirt-4.4.5Keywords: FutureFeature
Target Release: 4.4.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-14 11:40:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 902971    

Description Gordon Watson 2021-02-09 14:55:31 UTC 
Description of problem:

In 4.4, the LSM flow has apparently changed such that internal volumes are now copied, via CopyVolumeDataVDSCommand, on any host, not the SPM.

As such, we (Customer Support) need to know which host is being used so that we can request a sosreport from the right host. Currently, the only way to do this is to get a LogCollector, extract the engine logs, find the appropriate CopyVolumeDataVDSCommand entry and see which host was used. This will add quite a delay in analysing the problem and is not a simple procedure.

So, I'm suggesting that we add an audit log entry as part of the LSM flow, which is associated with the correlation id, that shows the host being used. That way, the customer could check the event log and let us know, or failing that, we could have them run a simple sql command to find it.



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

RHV 4.4


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 12 Ahmad Khiet 2021-03-15 11:51:25 UTC 
Hi 

create a vm with a disk.

turn on the vm:
from the disks subtab under the VM, move the VM disk to another storage domain.

expected result as shown in the screenshot[1]



shutdown the VM:
from the disks subtab under the VM, move the VM disk to another storage domain.
expected result as shown in the screenshot[1]


the attached gif shows the scenario with the VM is up.

(see the screenshot[1] and the gif https://imgur.com/a/vzq3o3G)
Comment 18 errata-xmlrpc 2021-04-14 11:40:02 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