Description of problem: When importing a VM without a disk from an import domain, the "VM imported successfully" audit log is not logged like when importing a VM that contains disks Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Export a VM without disks to an export domain 2. Delete the VM from the system 3. Import the VM from the export domain Actual results: A "Starting to import.." audit log appears but "VM imported successfully" audit log never appears even though the VM was imported successfully Expected results: The import successful audit log should be logged Additional info:
Works for me on current master (commit fc1714d). Moving to ON_QA to verify.
Created attachment 1304742 [details] 2 snapshots, engine.log Performed scenario described in comment 0, with the following builds: ovirt-engine-4.2.0-0.0.master.20170725202023.git561151b.el7.centos.noarch vdsm-4.20.1-218.git1b7671f.el7.centos.x86_64 When importing a vm that has no disks, there is a tiny alert on the upper-right side stating "FinishedImporting VM vm_name to Cluster cluster_name" (snapshot: 1. importing-vm-without-disks) There is no audit log message "VM imported successfully" (snapshot: 2. events) (also engine.log has no such message)
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
(In reply to Natalie Gavrielov from comment #2) > When importing a vm that has no disks, there is a tiny alert on the > upper-right side stating "FinishedImporting VM vm_name to Cluster > cluster_name" (snapshot: 1. importing-vm-without-disks) > There is no audit log message "VM imported successfully" (snapshot: 2. > events) > (also engine.log has no such message) Now I understand what I was misunderstanding, thanks!
Verified using build: ovirt-engine-4.2.0-0.0.master.20170929123516.git007c392.el7.centos.noarch
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.