Bug 1031553 - Port mirroring checkbox should be greyed out for update if that VNIC profile is located on VM
Summary: Port mirroring checkbox should be greyed out for update if that VNIC profile ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 3.4.1
Assignee: Alona Kaplan
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-18 09:42 UTC by GenadiC
Modified: 2014-07-30 06:55 UTC (History)
12 users (show)

Fixed In Version: av3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-08 13:36:18 UTC
oVirt Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 24896 0 None None None Never
oVirt gerrit 25387 0 None MERGED webadmin: Edit vNic Profile- disable pm if the profile is used by a vm Never

Description GenadiC 2013-11-18 09:42:23 UTC 
Description of problem:
When trying to update port mirroring for VNIC profile instead of getting an error message that the VNIC profile is located on VM, this checkbox should be disabled

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create VNIC profile with port mirroring disabled
2. Attach it to VM
3. Try to update port mirroring to enable for that VNIC profile

Actual results:
You get an error message that it is impossible to update VNIC profile

Expected results:
Check box of port mirroring for VNIC profile located on VM should be disabled

Additional info:
Comment 1 GenadiC 2014-03-16 14:37:44 UTC 
Verified in av3
Comment 2 Sandro Bonazzola 2014-05-08 13:36:18 UTC 
This is an automated message

oVirt 3.4.1 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.