Bug 1477963 - Export of VM without disks does not log the export success
Summary: Export of VM without disks does not log the export success
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Eyal Shenitzky
QA Contact: Natalie Gavrielov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-03 10:40 UTC by Natalie Gavrielov
Modified: 2017-12-20 11:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:44:59 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
engine.log (135.52 KB, application/zip)
2017-08-03 10:40 UTC, Natalie Gavrielov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1429499 0 unspecified CLOSED Import of VM without disks does not log the import success 2021-02-22 00:41:40 UTC
oVirt gerrit 80685 0 master MERGED core: Add callback mechanism to ExportVmCommand 2017-09-24 18:32:01 UTC

Internal Links: 1429499

Description Natalie Gavrielov 2017-08-03 10:40:30 UTC
Created attachment 1308681 [details]
engine.log

Description of problem:
Following issue 1429499, I noticed that the same goes for exporting a "diskless" VM:
When exporting a VM without any disks attached, the "Vm vm_name was exported successfully to export_domain" audit log is not logged like when exporting a VM that has disks.

Version-Release number of selected component:
ovirt-engine-4.2.0-0.0.master.20170725202023.git561151b.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
Export a VM without disks to an export domain.

Actual results:
No "exported successfully" audit log message.

Expected results:
"Vm vm_name was exported successfully to export_domain" audit log message should be logged.

Comment 1 Yaniv Kaul 2017-10-29 11:25:44 UTC
Is this correctly targeted for 4.3?

Comment 2 Allon Mureinik 2017-10-29 11:27:13 UTC
(In reply to Yaniv Kaul from comment #1)
> Is this correctly targeted for 4.3?
No, this is a mistake. It's merged to 4.2.

Comment 3 Natalie Gavrielov 2017-10-31 12:18:18 UTC
Verified, ovirt-engine-4.2.0-0.0.master.20171030210714.gitef6bb9c.el7.centos.noarch.

Comment 4 Sandro Bonazzola 2017-12-20 11:44:59 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


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