Created attachment 1094870 [details] node introspection screenshot Description of problem: After introspection the ironic nodes end up having 2 ports. It looks from the console output during introspection that there's created an ironic port for each interface that got an IP address via DHCP. Version-Release number of selected component (if applicable): openstack-ironic-api-4.2.0-2.1.el7ost.noarch python-ironicclient-0.8.1-1.el7ost.noarch python-ironic-inspector-client-1.2.0-4.el7ost.noarch openstack-ironic-common-4.2.0-2.1.el7ost.noarch openstack-ironic-inspector-2.2.2-1.el7ost.noarch openstack-ironic-conductor-4.2.0-2.1.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Register ironic nodes that have 1 nic connected to the provisioning network and another nic connected to a network that provides DHCP services 2. openstack baremetal introspection bulk start 3. ironic node-port-list 31ddb925-8ea7-4655-aee6-c6207aa1f362 Actual results: +--------------------------------------+-------------------+ | UUID | Address | +--------------------------------------+-------------------+ | ab41f108-1808-4217-9e65-65333f56b2a5 | a0:36:9f:22:e7:50 | | bde12d5c-a639-4f42-8679-13794d81b99f | f0:4d:a2:73:2f:b1 | +--------------------------------------+-------------------+ Expected results: Only the port with the mac address connected to the provisioning exists. Additional info: Attaching a screenshot from the introspection process and the ironic-inspector.log.
Created attachment 1094871 [details] inspector.log
Yeah, I see boot_interface set to None in data received from IPA.
Seems relate to https://bugs.launchpad.net/ironic/+bug/1405131
Seems like BOOTIF variable is no longer passed after we've moved ironic-inspector installation to puppet.
Can someone please test the proposed patch https://review.openstack.org/#/c/247556/ by applying it to /usr/share/openstack-puppet/modules/ironic/ before installing the undercloud?
sasha has confirmed this patch works.
Environment: openstack-puppet-modules-7.0.1-2.el7ost.noarch The nodes in my setup have only one port now and this BZ can be verified from my POV.
Verifying based on comment #9.
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://rhn.redhat.com/errata/RHEA-2016-0603.html