Bug 1451272

Summary: enlarge default MAC pool of freshly-installed ovirt-engine
Product: [oVirt] ovirt-engine Reporter: Dan Kenigsberg <danken>
Component: Database.CoreAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.2CC: bugs, mburman
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
mburman: testing_plan_complete-
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 10:59:25 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:
Bug Depends On:    
Bug Blocks: 1388595    

Description Dan Kenigsberg 2017-05-16 09:31:06 UTC
Out of the box, ovirt creates a default cluster with a default mac pool of size 96. This is typically to small.

Let us edit dbscripts/data/00220_insert_mac_pool_ranges.sql so that new installations have more macs by default.

00:1a:4a:16:01:00 — 00:1a:4a:16:04:ff (1024 macs) is a more reasonable size.

Comment 1 Michael Burman 2017-07-04 12:22:21 UTC
Verified on - 4.2.0-0.0.master.20170702100738.git46a9f67.el7.centos
The default MAC Addresses Range now for freshly-installed ovirt-engine is 
00:1a:4a:16:01:00 — 00:1a:4a:16:04:ff (1024 macs)

Comment 2 Sandro Bonazzola 2017-12-20 10:59:25 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.