Bug 1330140

Summary: [Text] - Bug in the error message when trying to update/edit network that is used by VM
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Dominik Holler <dholler>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: medium    
Version: 4.0.0CC: bugs, danken, dholler, mburman, michal.skrivanek
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3?
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-09 09:59:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log and screenshot
none
screenshots of ovirt-4.3 none

Description Michael Burman 2016-04-25 12:50:03 UTC
Created attachment 1150459 [details]
engine log and screenshot

Description of problem:
[Text] - Bug in the error message when trying to update/edit network that is used by VM. 

If trying to edit a network via the Networks main tab and the network is currently being used by a VM, the next error message is displayed -->

Error while executing action: Cannot edit Network. This logical network is used by virtual machines: (${ACTION_TYPE_FAILED_NETWORK_IN_ONE_USE_LIST_COUNTER}): ${ACTION_TYPE_FAILED_NETWORK_IN_ONE_USE_LIST}
- Please detach virtual machines using this logical network and try again.


Version-Release number of selected component (if applicable):
4.0.0-0.0.master.20160423161403.gite38df80.el7.centos

How reproducible:
100

Steps to Reproduce:
1. Attach VM network to host via setup networks
2. Add vNIC with network to VM and run it
3. Via the 'Networks' main tab, try to edit the network to be non-VM network
or try to rename the network. 

Actual results:
Error while executing action: Cannot edit Network. This logical network is used by virtual machines: (${ACTION_TYPE_FAILED_NETWORK_IN_ONE_USE_LIST_COUNTER}): ${ACTION_TYPE_FAILED_NETWORK_IN_ONE_USE_LIST}
- Please detach virtual machines using this logical network and try again.

Expected results:
Should see the name of the VMs that are using this logical network

Comment 1 Red Hat Bugzilla Rules Engine 2016-04-25 16:15:52 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Red Hat Bugzilla Rules Engine 2016-05-01 13:46:28 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Sandro Bonazzola 2016-05-02 09:50:31 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 4 Yaniv Lavi 2016-05-23 13:14:24 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 5 Michal Skrivanek 2016-06-14 21:22:49 UTC
Not a GA blocker

Comment 6 Dominik Holler 2019-01-09 09:32:15 UTC
Created attachment 1519393 [details]
screenshots of ovirt-4.3

Comment 7 Dominik Holler 2019-01-09 09:33:54 UTC
I am unable to reproduce this bug, do you know if the bug still reproduces?

Comment 8 Michael Burman 2019-01-09 09:57:18 UTC
(In reply to Dominik Holler from comment #7)
> I am unable to reproduce this bug, do you know if the bug still reproduces?

Looks like the bug was fixed by someone along the way)

The text in the error message look ok now on 4.3.0-0.6.alpha2.el7

"Error while executing action: Cannot edit Network. This logical network is used by virtual machine: Shiva1
- Please remove it from this virtual machine and try again."

"Error while executing action: Cannot edit Network. This logical network is used by virtual machines: (2): Shiva1,
Shiva3
- Please detach virtual machines using this logical network and try again."

Feel free to close this as current release)