Red Hat Bugzilla – Bug 1023952
[RFE] [RHEVM][webadmin] vNIC profile screens are missing features
Last modified: 2016-02-10 14:48:40 EST
Description of problem:
When creating/editing a vNIC profile, the displayed fields are affected by the version of the data center, while they should be verion agnostic since they should be blocked by cluster version.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a 3.0 DC
2. Create a new or edit the management network's vNIC profile
The profile screen has no option to select "Port mirroring".
There is no way to add custom properties.
It should be possible to select a port mirroring or add custom properties.
The version enforcement should be done by can do action when adding/editing vNIC
Port mirroring is 3.1 feature so I think it's better to enforce it on the vNIC profile creation level.
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.