Red Hat Bugzilla – Bug 1270583
Vm nic unplugged after previewing/undoing a snapshot
Last modified: 2016-02-10 14:15:34 EST
Created attachment 1081794 [details]
Description of problem:
When previewing a vm snapshot, the vm nic is unplugged
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a vm with 1 disk
2. make snapshot
3. preview the snapshot
The vm nic is unplugged
Raz, this should both have network whiteboard, and on BLL.Network component.
Please fix that.
Also happens after undoing a previewed snapshot
*** Bug 1272056 has been marked as a duplicate of this bug. ***
The vm nic is also unplugged after a vm is imported, reproducible 100% in 3.6.0-17 build RHEL 7.2.
@Barak: Should I open a new bug or do you think this issue has the same root cause?
could you reply to comment 5?
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
in reply to comment5: it's very probable, that this has the same cause. I just need to do some testing and patch should be ready.
please when testing this, you might want to retest scenarion in bug https://bugzilla.redhat.com/1212461
since changes there caused this issue.
This bug is referenced in git log for ovirt-engine-22.214.171.124.
Please set target release to 126.96.36.199 accordingly unless additional patches are needed.
*** Bug 1286687 has been marked as a duplicate of this bug. ***
Please note that I'm also hitting his issue with VMs imported from an export domain (I verified that the original VM has a plugged NIC)
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Verified on - 188.8.131.52-0.1.el6
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.
*** Bug 1293297 has been marked as a duplicate of this bug. ***