Eldan suggested to override the currently-existing per-VM exclamation mark: if a VM has a vnic with a mac address outside of the relevant pool, an "!" would show to the left of the VM line. A new exclamation mark would be added to the left of the offending vnic. On mac pool editing dialog, it would be nice to add a warning with a counter: "X vnics are defined outside of mac pool ranges"
(In reply to Dan Kenigsberg from comment #4) > Eldan suggested to override the currently-existing per-VM exclamation mark: > if a VM has a vnic with a mac address outside of the relevant pool, an "!" > would show to the left of the VM line. > > A new exclamation mark would be added to the left of the offending vnic. > > On mac pool editing dialog, it would be nice to add a warning with a > counter: "X vnics are defined outside of mac pool ranges" This should be visible from the main VM grid.
*** Bug 1295867 has been marked as a duplicate of this bug. ***
For verification: please make sure you check the v2v flow described in bug 1295867 as well
Completely missed 3.6.6. Any chance for 3.6.7?
Created attachment 1163237 [details] Script that finds VMs with external MACs on their vNICs for ovirt-engine v3.6 The script finds out all VMs that has an external MAC address defined on one of the vNICs. The outputs of the script are: * List of problematic VM/vNIC/MAC address * Search query string to be used in the web-admin search Note: It requires ovirt-engine-python-sdk to be installed on the computer that the script is run from.
Created attachment 1163240 [details] Script that finds VMs with external MACs on their vNICs for ovirt-engine v4
Comment on attachment 1163240 [details] Script that finds VMs with external MACs on their vNICs for ovirt-engine v4 Please note that the v4 script requires python-ovirt-engine-sdk4 package to be installed on the computer that runs the script.
Paul, Could you please check with your customer if the provided scripts answer his need?
(In reply to Yaniv Dary from comment #5) > This should be visible from the main VM grid.
(In reply to Yevgeny Zaspitsky from comment #14) > Paul, > Could you please check with your customer if the provided scripts answer his > need? How can the customer test it, if it's uses v4 SDK?
There are two versions of the script - one for v4 and another one for v3.6. Both versions are attached to this bug.
The script is intended as an immediate remedy to systems that already have VMs with out-of-range MACs. Having the main VM grid indicate which VM is out-of-range (and searching for all VMs that have this indication), is too complicated to solve in a timely manner. Alerting about out-of-range VMs during import process is more feasible; Showing an alert whenever such a VM is started may spam people that intentionally have manual MAC.
The down side of alerting on each startup is that it spams the audit log in case someone actually needs to use an out-of-range mac. At this stage, I'd rather limit our warning to the mass import use-case.
Please make sure to clone the bug to 3.6.8, its possible even when bug is on POST.
Should this be on qa?
I've cloned bug 1362589 to track what we believe is the fully-fledged feature (UI included). For 4.0-ga we are shipping only event-log alerts when an out-of-range VM is imported.
Verified on 4.0.2.4-0.1.el7ev (import from export domain)
Also verified when importing from VMware, Xen and KVM
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. https://rhn.redhat.com/errata/RHEA-2016-1743.html