Bug 1298299

Summary: [RFE] ability to use multiple ranges in a subnet
Product: Red Hat Satellite Reporter: David Juran <djuran>
Component: NetworkingAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1.5CC: bkearney, ktordeur, mhulan
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/10949
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-17 14:49:12 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:

Description David Juran 2016-01-13 17:06:17 UTC 
Description of problem:
Occasionally a customer may want to deploy hosts to a fragmented subnet where several free "holes" exist. In a subnet definition, as it looks today, it is only possible to define a single range in a subnet in which the satellite can create hosts. The ability to specify multiple ranges would be useful


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



Additional info:
The issue can currently be worked around by manually reserving the used IP:s in the DHCP configuration. Nevertheless, the ability to do this using the web UI would be nice.
Comment 1 Bryan Kearney 2016-04-13 19:54:49 UTC 
Created redmine issue http://projects.theforeman.org/issues/14627 from this bug
Comment 2 Bryan Kearney 2016-07-26 19:06:54 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 3 Bryan Kearney 2016-08-10 19:12:48 UTC 
Upstream bug component is Other
Comment 4 Bryan Kearney 2016-08-10 20:13:48 UTC 
Upstream bug component is Provisioning
Comment 5 Bryan Kearney 2016-08-10 22:13:26 UTC 
Upstream bug component is Other
Comment 6 Bryan Kearney 2016-08-18 14:12:09 UTC 
Upstream bug component is Networking
Comment 7 Marek Hulan 2016-10-03 11:06:00 UTC 
This should be possible with Satellite 6.2 by defining multiple subnets with different range, since the validation on network range has been removed. Would that be a sufficient solution?
Comment 8 Bryan Kearney 2018-07-17 14:49:12 UTC 
PLease see comment 7. If this is not sufficient, please re-open.