Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1063711

Summary: [engine-config] no values for versions 3.2 and up for EnableMACAntiSpoofingFilterRules
Product: [Retired] oVirt Reporter: Meni Yakove <myakove>
Component: ovirt-engine-configAssignee: Moti Asayag <masayag>
Status: CLOSED CURRENTRELEASE QA Contact: GenadiC <gcheresh>
Severity: high Docs Contact:
Priority: high    
Version: 3.4CC: acathrow, gcheresh, gklein, iheim, masayag, sraje, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.4.0Flags: masayag: ovirt_requires_release_note+
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: ovirt-3.4.0-beta3 Doc Type: Bug Fix
Doc Text:
Cause: An internal configuration value was exposed via the engine-config utility, allowing the user to define in which cluster levels the no-mac-spoofing feature should be enabled. Consequence: The user would be able to enable the feature for 3.0 clusters in which the api isn't supported and causing the vm run to fail. Fix: The configuration value EnableMACAntiSpoofingFilterRules was changed to be a system-wide. Either no-mac-spoofing will be enabled to all of the vms which their cluster level supports, or to none if the feature is disabled. Result: As a result of this fix, if a user disabled the feature on his environment, the original default value will be restored, meaning the feature will be enabled after the upgrade. The user should disable it again using the engine-config, without specifying a version: engine-config -s EnableMACAntiSpoofingFilterRules=true The reason no upgrade script is suggested for that matter relies on the fact that there is no a clear way of how to upgrade a mix cluster support, as originally (and mistakenly) was exposed to the user.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-31 12:31:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Meni Yakove 2014-02-11 10:06:25 UTC 
Description of problem:
There is no values for versions 3.2 and up in engine-config for EnableMACAntiSpoofingFilterRules

engine-config  -g EnableMACAntiSpoofingFilterRules
EnableMACAntiSpoofingFilterRules: false version: 3.0
EnableMACAntiSpoofingFilterRules: false version: 3.1

When trying to enable/disable EnableMACAntiSpoofingFilterRules for 3.4 version:
engine-config  -s EnableMACAntiSpoofingFilterRules=true  --cver 3.4
Error setting EnableMACAntiSpoofingFilterRules's value. No such entry with version 3.4.

Version-Release number of selected component (if applicable):
ovirt-engine-3.4.0-0.7.beta2.el6.noarch
Comment 1 Sandro Bonazzola 2014-03-03 15:23:51 UTC 
This is an automated message.

This BZ should be fixed in oVirt 3.4.0 RC repository, assignee please update the status of the bug to ON_QA once you've verified that the change is included in the build.
Comment 2 GenadiC 2014-03-04 15:03:45 UTC 
Verified in av2
Comment 3 Sandro Bonazzola 2014-03-31 12:31:09 UTC 
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released