Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1270033

Summary: [RDO-Manager] Node inspection fails when changing the default 'inspection_iprange' value in undecloud.conf.
Product: [Community] RDO Reporter: Omri Hochman <ohochman>
Component: instack-undercloudAssignee: James Slagle <jslagle>
Status: CLOSED CURRENTRELEASE QA Contact: Shai Revivo <srevivo>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: chris.brown, ibravo, jtrowbri, mburns
Target Milestone: ---   
Target Release: Liberty   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: instack-undercloud-2.1.3-dev225 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-18 06:02:47 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 Omri Hochman 2015-10-08 20:44:04 UTC 
[RDO-Manager] Node inspection fails when changing the default 'inspection_iprange' value in undecloud.conf.


Environment:
------------
instack-undercloud-2.1.3-dev224.el7.centos.noarch
instack-0.0.8-dev4.el7.centos.noarch
openstack-ironic-inspector-2.2.1-dev7.el7.centos.noarch
openstack-ironic-common-4.2.1-dev26.el7.centos.noarch
python-ironic-inspector-client-1.2.1-dev6.el7.centos.noarch
python-ironicclient-0.8.2-dev14.el7.centos.noarch


Description:
-------------

(1) In undercloud.conf change the default values of 'inspection_iprange'  
Example:inspection_iprange = 192.168.0.100,192.168.0.120

(2) Attempt to run : openstack baremetal introspection bulk start - 

Results:
---------
the machines fail to boot to PXE and interception fails on timeout  

The reason:
-----------
The value under /etc/ironic-inspector/dnsmasq.conf  remains with the default value -->  dhcp-range=192.0.2.100,192.0.2.120,29
Comment 1 John Trowbridge 2015-10-12 14:16:31 UTC 
This was fixed with the switch to puppet.
Comment 2 Ignacio Bravo 2015-10-14 13:03:45 UTC 
*** Bug 1269606 has been marked as a duplicate of this bug. ***
Comment 3 Mike McCune 2016-03-28 22:50:27 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 5 Christopher Brown 2017-06-17 19:42:53 UTC 
(In reply to John Trowbridge from comment #1)
> This was fixed with the switch to puppet.

So I guess this can be closed then. :)