Ask Your Question
0

TripleO introspection failed with timeout.

asked 2017-08-20 17:55:04 -0600

Aqsa gravatar image

updated 2017-08-22 15:07:36 -0600

rbowen gravatar image

I am installing TripleO on baremetal. The introspection is failing with a timeout. The ironic inspector logs are not showing anything meaningful. The dnsmasq logs are showing something like this

Aug 19 13:12:03 dnsmasq-dhcp[2029]: 3230848440 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:12:03 dnsmasq-dhcp[2029]: 3230848440 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:12:03 dnsmasq-dhcp[2029]: 3230848440 DHCPDISCOVER(tap96e37443-fc) 90:e2:ba:92:d5:b8 no address available
Aug 19 13:12:04 dnsmasq-dhcp[2029]: 3230846480 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:12:04 dnsmasq-dhcp[2029]: 3230846480 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:12:05 dnsmasq-dhcp[2029]: 3230848440 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:12:05 dnsmasq-dhcp[2029]: 3230848440 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:12:38 dnsmasq-dhcp[2029]: 2926653479 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:12:38 dnsmasq-dhcp[2029]: 2926653479 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:12:38 dnsmasq-dhcp[2029]: 2926653479 user class: iPXE
Aug 19 13:12:38 dnsmasq-dhcp[2029]: 2926653479 DHCPDISCOVER(tap96e37443-fc) 90:e2:ba:92:ce:10 no address available
Aug 19 13:12:40 dnsmasq-dhcp[2029]: 1346472988 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:12:40 dnsmasq-dhcp[2029]: 1346472988 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:12:40 dnsmasq-dhcp[2029]: 1346472988 user class: iPXE
Aug 19 13:12:40 dnsmasq-dhcp[2029]: 1346472988 DHCPDISCOVER(tap96e37443-fc) 90:e2:ba:92:d5:b8 no address available
Aug 19 13:12:46 dnsmasq-dhcp[2029]: 2926653479 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:12:46 dnsmasq-dhcp[2029]: 2926653479 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:12:46 dnsmasq-dhcp[2029]: 2926653479 user class: iPXE
Aug 19 13:12:48 dnsmasq-dhcp[2029]: 1346472988 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:12:48 dnsmasq-dhcp[2029]: 1346472988 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:12:48 dnsmasq-dhcp[2029]: 1346472988 user class: iPXE
Aug 19 13:14:01 dnsmasq-dhcp[2029]: 3247623696 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:14:01 dnsmasq-dhcp[2029]: 3247623696 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:14:01 dnsmasq-dhcp[2029]: 3247623696 DHCPDISCOVER(tap96e37443-fc) 90:e2:ba:92:ce:10 no address available
Aug 19 13:14:03 dnsmasq-dhcp[2029]: 3247623696 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:14:03 dnsmasq-dhcp[2029]: 3247623696 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:14:16 dnsmasq-dhcp[2029]: 3230848440 available DHCP subnet: 192.168.98.0/255.255.255.0
Aug 19 13:14:16 dnsmasq-dhcp[2029]: 3230848440 vendor class: PXEClient:Arch:00000:UNDI:002001
Aug 19 13:14:16 dnsmasq-dhcp[2029]: 3230848440 DHCPDISCOVER(tap96e37443-fc ...
(more)
edit retag flag offensive close merge delete

Comments

Hi, seems like the node is not getting DHCP IP hence PXE boot is not happening !!

CloudEnthusiast gravatar imageCloudEnthusiast ( 2017-08-22 06:00:51 -0600 )edit

3 answers

Sort by ยป oldest newest most voted
0

answered 2018-08-31 06:20:17 -0600

vinothkumar gravatar image

Disable DHCP on your physical router level and use the dhcp range start and end on your undercloud.conf file.

Ensure that IPMI and PXE network VLAN should be Native VLAN.

edit flag offensive delete link more
0

answered 2018-08-21 08:43:29 -0600

(For the files) One workaround that worked for me:

In my environment the PXE boot itself worked, but the DHCP requests for initialization of the different interfaces did not work. After increasing the DHCP timeout from default 30 seconds to 5 minutes the problem was gone. (I never found the real root cause...)

To increase the timeout, you have to set the environment following variable before creating the images with diskimage-builder:

export DIB_DHCP_TIMEOUT=300
edit flag offensive delete link more
0

answered 2017-10-17 06:47:47 -0600

MustafaArif gravatar image

updated 2017-10-17 06:48:45 -0600

Possible flow of troubleshooting this problem is

  • Look to the sever console if it is able to get the DHCP IP address from director node if it is not getting please check following things

a. The VLAN which you are using for introspection is native untagged VLAN

b. tcpdump on director node will give you insight if you are getting DHCP request from the node, if yes then director should send the DHCP response

  • It may also happen that your node is able to download the image but is not able to end the introspection data collection, it can get to hang state. This will result in your node not sending introspected data back to director and post default timeout the introspection will fail with timeout error.
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-08-20 17:55:04 -0600

Seen: 882 times

Last updated: Aug 31