Bug 1926854 - [RFE] Requesting an audit log entry be added in LSM flow to display the host on which the internal volumes are copied
Summary: [RFE] Requesting an audit log entry be added in LSM flow to display the host ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.4.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.5
: 4.4.5
Assignee: Ahmad Khiet
QA Contact: sshmulev
URL:
Whiteboard:
Depends On:
Blocks: 902971
TreeView+ depends on / blocked
 
Reported: 2021-02-09 14:55 UTC by Gordon Watson
Modified: 2024-06-14 00:13 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-14 11:40:02 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:1169 0 None None None 2021-04-14 11:40:27 UTC
oVirt gerrit 113598 0 master MERGED core: log copy volume data host to audit log 2021-03-01 12:29:58 UTC
oVirt gerrit 113795 0 master MERGED core: [fix] log copy volume data host to audit log 2021-03-09 11:05:48 UTC

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


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