Bug 1382522 - Introspection on BM doesn't complete, the introspected node throws "http://192.0.2.1:8088/inspector.ipxe... Connection reset"
Summary: Introspection on BM doesn't complete, the introspected node throws "http://19...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 10.0 (Newton)
Assignee: Dmitry Tantsur
QA Contact: Raviv Bar-Tal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 22:18 UTC by Alexander Chuzhoy
Modified: 2017-12-19 00:47 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 09:05:25 UTC
Target Upstream Version:

Attachments (Terms of Use)
sosreport from the undercloud node (9.77 MB, application/x-xz)
2016-10-06 23:34 UTC, Alexander Chuzhoy 		no flags Details
inspector.ipxe (490 bytes, text/plain)
2016-10-07 13:24 UTC, Alexander Chuzhoy 		no flags Details
undercloud.conf from the undercloud node (10.39 KB, text/plain)
2016-10-12 13:56 UTC, Alexander Chuzhoy 		no flags Details
the requested tcpdump (217.10 KB, text/plain)
2016-10-12 14:32 UTC, Alexander Chuzhoy 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alexander Chuzhoy 2016-10-06 22:18:55 UTC 
rhel-osp-director:   Introspection on BM doesn't complete, The introspected node throws "http://192.0.2.1:8088/inspector.ipxe... Connection reset"

Environment:
openstack-ironic-common-6.2.1-0.20160930163405.3f54fec.el7ost.noarch
python-ironicclient-1.7.0-0.20160916002722.464044f.el7ost.noarch
puppet-ironic-9.4.0-1.el7ost.noarch
instack-undercloud-5.0.0-0.20160930175750.9d2a655.el7ost.noarch
python-ironic-inspector-client-1.9.0-0.20160916002438.6364bc9.el7ost.noarch
openstack-ironic-conductor-6.2.1-0.20160930163405.3f54fec.el7ost.noarch
dnsmasq-utils-2.66-14.el7_1.x86_64
openstack-ironic-api-6.2.1-0.20160930163405.3f54fec.el7ost.noarch
dnsmasq-2.66-21.el7.x86_64
openstack-ironic-inspector-4.2.1-0.20160922151040.36900fb.el7ost.noarch
python-ironic-lib-2.1.0-0.20160915122034.52b2d2f.el7ost.noarch


Steps to reproduce:
Try to introspect nodes on BM setup.

Result:
The introspection doesn't finish.
Seeing this on the console:
Filename: http://192.0.2.1:8088/inspector.ipxe
http://192.0.2.1:8088/inspector.ipxe... Connection reset (http://ipxe.org/0f0a6039)
No more network devices
Comment 1 Alexander Chuzhoy 2016-10-06 22:21:44 UTC 
The issue reproduces on different BM setups.
Comment 2 Alexander Chuzhoy 2016-10-06 23:34:30 UTC 
Created attachment 1208060 [details]
sosreport from the undercloud node
Comment 3 Dmitry Tantsur 2016-10-07 09:56:48 UTC 
Can you fetch http://192.0.2.1:8088/inspector.ipxe from undercloud? Is it the same issue where flushing iptables rules helped you?
Comment 5 Alexander Chuzhoy 2016-10-07 13:24:55 UTC 
Created attachment 1208154 [details]
inspector.ipxe
Comment 6 Alexander Chuzhoy 2016-10-07 13:26:23 UTC 
After flushing iptables on the undercloud, I didn't see this error, but the introspection didn't finish either - was gathering data in loop.
Comment 7 Dmitry Tantsur 2016-10-07 13:53:10 UTC 
Sorry, I just realized my question was confusing. I meant, can you try fetching http://192.0.2.1:8088/inspector.ipxe using curl from the undercloud? Will it work?

The problem after flushing iptables - do you see any errors in the machine's console? Does it fail to post data back?
Comment 9 Alexander Chuzhoy 2016-10-08 04:59:17 UTC 
Tried it on another BM setup (different IP):
[root@undercloud ~]# curl http://192.168.0.1:8088/inspector.ipxe                                                                                                                                                     
#!ipxe                                                                                                                                                                                                               

:retry_dhcp
dhcp || goto retry_dhcp

:retry_boot
imgfree    
kernel --timeout 60000 http://192.168.0.1:8088/agent.kernel ipa-inspection-callback-url=http://192.168.0.1:5050/v1/continue ipa-inspection-collectors=default,extra-hardware,logs systemd.journald.forward_to_console=yes BOOTIF=${mac} ipa-debug=1 ipa-inspection-dhcp-all-interfaces=1 ipa-collect-lldp=1 initrd=agent.ramdisk || goto retry_boot                                                                                       
initrd --timeout 60000 http://192.168.0.1:8088/agent.ramdisk || goto retry_boot                                                                                                                                      
boot                                                                                                                                                                                                                 
After flushing the iptables (sudo iptables -F), no improvement.
I also tried to replace /tftpboot/undionly.kpxe with http://boot.ipxe.org/undionly.kpxe
Comment 11 Raviv Bar-Tal 2016-10-10 07:09:31 UTC 
We have fail to reproduce this issue on tlv systems, both the original system and second system I have(Raviv).

Shasha - can you reproduce the same problem on your system?
Comment 14 Alexander Chuzhoy 2016-10-11 15:55:57 UTC 
The problem still reproduces on my setup:
openstack-ironic-common-6.2.1-0.20160930163405.3f54fec.el7ost.noarch
puppet-ironic-9.4.0-1.el7ost.noarch
python-ironicclient-1.7.0-1.el7ost.noarch
instack-undercloud-5.0.0-0.20160930175750.9d2a655.el7ost.noarch
python-ironic-inspector-client-1.9.0-1.el7ost.noarch
openstack-ironic-conductor-6.2.1-0.20160930163405.3f54fec.el7ost.noarch
openstack-ironic-api-6.2.1-0.20160930163405.3f54fec.el7ost.noarch
openstack-ironic-inspector-4.2.1-0.20160922151040.36900fb.el7ost.noarch
python-ironic-lib-2.1.0-1.el7ost.noarch
Comment 16 Dmitry Tantsur 2016-10-11 15:59:44 UTC 
Ok, can you see any signs of the HTTP request arriving? Please check both httpd logs and tcpdump. If yes, do you see signs of a response (again, tcpdump or anything alike)?
Comment 17 Alexander Chuzhoy 2016-10-11 16:47:11 UTC 
Nothing got appended to:
/var/log/httpd/ipxe_vhost_access.log
/var/log/httpd/ipxe_vhost_error.log


snap from journalctl -f -u openstack-ironic-inspector-dnsmasq:

Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.100 00:0a:f7:79:93:2a
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.100 00:0a:f7:79:93:2a
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.102 00:0a:f7:79:93:1a
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.102 00:0a:f7:79:93:1a
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.101 00:0a:f7:79:93:18
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.101 00:0a:f7:79:93:18
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.100 00:0a:f7:79:93:2a
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.100 00:0a:f7:79:93:2a
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.102 00:0a:f7:79:93:1a
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.102 00:0a:f7:79:93:1a
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.101 00:0a:f7:79:93:18
Oct 11 12:43:04 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.101 00:0a:f7:79:93:18
Oct 11 12:43:38 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPDISCOVER(br-ctlplane) 00:0a:f7:7f:24:88
Oct 11 12:43:38 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPOFFER(br-ctlplane) 192.168.0.103 00:0a:f7:7f:24:88
Oct 11 12:43:41 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPDISCOVER(br-ctlplane) 00:0a:f7:7f:24:96
Oct 11 12:43:41 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPOFFER(br-ctlplane) 192.168.0.104 00:0a:f7:7f:24:96
Oct 11 12:43:44 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPDISCOVER(br-ctlplane) 00:0a:f7:7f:24:9e
Oct 11 12:43:44 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPOFFER(br-ctlplane) 192.168.0.105 00:0a:f7:7f:24:9e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPDISCOVER(br-ctlplane) 00:0a:f7:7f:24:5e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPOFFER(br-ctlplane) 192.168.0.106 00:0a:f7:7f:24:5e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.103 00:0a:f7:7f:24:88
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.103 00:0a:f7:7f:24:88
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.103 00:0a:f7:7f:24:88
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.103 00:0a:f7:7f:24:88
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.105 00:0a:f7:7f:24:9e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.105 00:0a:f7:7f:24:9e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.103 00:0a:f7:7f:24:88
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.103 00:0a:f7:7f:24:88
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.104 00:0a:f7:7f:24:96
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.104 00:0a:f7:7f:24:96
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.105 00:0a:f7:7f:24:9e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.105 00:0a:f7:7f:24:9e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.104 00:0a:f7:7f:24:96
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.104 00:0a:f7:7f:24:96
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.105 00:0a:f7:7f:24:9e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.105 00:0a:f7:7f:24:9e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.104 00:0a:f7:7f:24:96
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.104 00:0a:f7:7f:24:96
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.103 00:0a:f7:7f:24:88
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.103 00:0a:f7:7f:24:88
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.105 00:0a:f7:7f:24:9e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.105 00:0a:f7:7f:24:9e
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPREQUEST(br-ctlplane) 192.168.0.104 00:0a:f7:7f:24:96
Oct 11 12:43:47 undercloud.localdomain dnsmasq-dhcp[31036]: DHCPACK(br-ctlplane) 192.168.0.104 00:0a:f7:7f:24:96


Snap from "tcpdump -i any port 67 or port 68 or port 69":
12:39:32.902350 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:9e (oui Unknown), length 548
12:39:32.902350 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:9e (oui Unknown), length 548
12:39:32.902714 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
12:39:32.902712 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
12:39:32.929055 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 331
12:39:32.929055 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 331
12:39:32.930964 IP 192.168.0.18.ah-esp-encap > undercloud.localdomain.tftp:  30 RRQ "undionly.kpxe" octet tsize 0
12:39:32.931080 IP 192.168.0.18.ah-esp-encap > undercloud.localdomain.tftp:  30 RRQ "undionly.kpxe" octet tsize 0
12:39:32.945874 IP 192.168.0.18.acp-port > undercloud.localdomain.tftp:  35 RRQ "undionly.kpxe" octet blksize 1456
12:39:32.945874 IP 192.168.0.18.acp-port > undercloud.localdomain.tftp:  35 RRQ "undionly.kpxe" octet blksize 1456
12:39:33.219670 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 302
12:39:33.219706 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 302
12:39:34.243014 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:5e (oui Unknown), length 548
12:39:34.243014 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:5e (oui Unknown), length 548
12:39:34.243589 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
12:39:34.243587 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300
12:39:34.278999 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 331
12:39:34.278999 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 331
12:39:36.225804 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 302
12:39:36.225826 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 302
12:39:37.973809 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:88 (oui Unknown), length 396
12:39:37.973809 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:88 (oui Unknown), length 396
12:39:37.974516 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 365
12:39:37.974516 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 365
12:39:37.974655 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 327
12:39:37.974664 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 327
12:39:39.163206 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:96 (oui Unknown), length 396
12:39:39.163206 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:96 (oui Unknown), length 396
12:39:39.163643 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 327
12:39:39.163658 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 327
12:39:39.164144 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 365
12:39:39.164144 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 365
12:39:39.612137 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:9e (oui Unknown), length 396
12:39:39.612137 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:9e (oui Unknown), length 396
12:39:39.612672 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 365
12:39:39.612672 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 365
12:39:39.612942 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 327
12:39:39.612953 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 327
12:39:40.897747 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:5e (oui Unknown), length 396
12:39:40.897747 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0a:f7:7f:24:5e (oui Unknown), length 396
12:39:40.898260 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 327
12:39:40.898274 IP undercloud.localdomain.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 327
12:39:40.898420 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 365
12:39:40.898420 IP 192.168.0.5.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 365
Comment 18 Dmitry Tantsur 2016-10-12 10:47:24 UTC 
> Nothing got appended to:
> /var/log/httpd/ipxe_vhost_access.log
> /var/log/httpd/ipxe_vhost_error.log

Ok, could you please check iPXE port (8088) with tcpdump as well?

For the record, I've also done a successful introspection on our hardware lab with the latest puddle. I think it must be something subtle about your environment. CC'ing Dan in case he has any ideas.
Comment 19 Bob Fournier 2016-10-12 13:42:40 UTC 
Alexander - could you please add undercloud.conf to bug?  Thank you.

Also, in looking at the attached sosreport it looks like the undercloud is using 192.168.0.1 (see below) on provisioning net, yet the nodes are trying to 
access 192.0.2.1?  Perhaps the sosreport is out of sync?

sosreport-undercloud.localdomain-20161006192524 bfournie$ cat ip_addr 
1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever
1: lo    inet6 ::1/128 scope host \       valid_lft forever preferred_lft forever
2: eth0    inet 10.19.184.221/24 brd 10.19.184.255 scope global dynamic eth0\       valid_lft 81936sec preferred_lft 81936sec
2: eth0    inet6 2620:52:0:13b8:5054:ff:fe3e:c994/64 scope global noprefixroute dynamic \       valid_lft 2591945sec preferred_lft 604745sec
2: eth0    inet6 fe80::5054:ff:fe3e:c994/64 scope link \       valid_lft forever preferred_lft forever
3: eth1    inet6 fe80::5054:ff:fe18:6679/64 scope link \       valid_lft forever preferred_lft forever
5: br-ctlplane    inet 192.168.0.1/24 brd 192.168.0.255 scope global br-ctlplane\       valid_lft forever preferred_lft forever
5: br-ctlplane    inet6 fe80::5054:ff:fe18:6679/64 scope link \       valid_lft forever preferred_lft forever
Comment 20 Alexander Chuzhoy 2016-10-12 13:56:00 UTC 
Created attachment 1209621 [details]
undercloud.conf from the undercloud node
Comment 21 Alexander Chuzhoy 2016-10-12 13:57:10 UTC 
Bob,
The details were taken from a setup that also hits the same bug.
This setup uses 192.168.0.0/24 (instead of 192.0.2.0) for provisioning net.
Comment 22 Alexander Chuzhoy 2016-10-12 14:32:23 UTC 
Created attachment 1209628 [details]
the requested tcpdump
Comment 23 Dan Sneddon 2016-10-12 19:32:42 UTC 
(In reply to Alexander Chuzhoy from comment #21)
> Bob,
> The details were taken from a setup that also hits the same bug.
> This setup uses 192.168.0.0/24 (instead of 192.0.2.0) for provisioning net.

Where are the baremetal environments where this problem was reproduced? I'm wondering if they have something in common (same hardware, same Ethernet switches, etc.).
Comment 24 Alexander Chuzhoy 2016-10-12 20:40:44 UTC 
I see the issue on a setup consisting of Dell PowerEdge R320.

Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe
Comment 25 Dmitry Tantsur 2016-10-13 08:20:22 UTC 
We also have PowerEdge R320, so the nodes are probably not to blame. Not sure about the switch though..
Comment 29 Alexander Chuzhoy 2016-10-13 21:03:07 UTC 
After switching to a newer version of RHEL 7.3 on the undercloud, I don't reproduce the issue.
Comment 30 Dmitry Tantsur 2016-10-14 09:05:25 UTC 
Thanks Sasha, let us assume that it was some bug in RHEL. Please feel free to reopen if you hit it again.
Comment 31 Alexander Chuzhoy 2017-12-19 00:47:49 UTC 
A very slow undercloud can cause this issue.
Note You need to log in before you can comment on or make changes to this bug.