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

Bug 1608563

Summary:	dhcp_start and dhcp_end should be optional for leaf definitions added to undercloud.conf
Product:	Red Hat OpenStack	Reporter:	Alexander Chuzhoy <sasha>
Component:	python-tripleoclient	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	Alexander Chuzhoy <sasha>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	15.0 (Stein)	CC:	bfournie, dbecker, dsneddon, hbrock, hjensas, jslagle, mburns, morazi, sclewis
Target Milestone:	Upstream M2	Keywords:	Triaged
Target Release:	15.0 (Stein)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-10.5.1-0.20190506170359.f08bfef.el8ost python-tripleoclient-11.4.1-0.20190503200354.0a85020.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-21 11:16:20 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 Alexander Chuzhoy 2018-07-25 20:04:28 UTC

dhcp_start and dhcp_end should be optional  for leaf definitions added to undercloud.conf


Currently the dhcp_start and dhcp_end are mandatory, but with the option to use predictive IP assignment across multiple subnets, these should become non-mandatory.

Environment:
instack-undercloud-8.4.1-4.el7ost.noarch
openstack-tripleo-heat-templates-8.0.2-35.el7ost.noarch

Comment 9 Alexander Chuzhoy 2019-09-18 19:29:28 UTC

Verified:
Version:
python3-tripleoclient-11.5.2-0.20190913030432.00fe507.el8ost.noarch
openstack-tripleo-heat-templates-10.6.2-0.20190913130451.e95a183.el8ost.noarch

Removed the following lines under leafs in undercloud.conf:
dhcp_start = 
dhcp_end = 

Ran: openstack undercloud install with no issue.

Comment 10 errata-xmlrpc 2019-09-21 11:16:20 UTC

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://access.redhat.com/errata/RHEA-2019:2811