ironic-ipxe looking for wrong file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Invalid
|
Undecided
|
Unassigned | ||
tripleo |
New
|
Undecided
|
Unassigned |
Bug Description
This is a very perplexing error. Ironic-pxe-tftboot for some reason is asking for the wrong files, i.e. the log file can look like such:
```
Sep 17 10:32:24 dnsmasq-tftp[2]: sent /var/lib/
Sep 17 10:45:13 dnsmasq-tftp[2]: file /var/lib/
Sep 17 11:55:15 dnsmasq-tftp[2]: error 8 User aborted the transfer received from 192.168.5.201
Sep 17 11:55:15 dnsmasq-tftp[2]: sent /var/lib/
Sep 17 11:55:15 dnsmasq-tftp[2]: sent /var/lib/
Sep 17 13:01:04 dnsmasq[2]: exiting on receipt of SIGTERM
Sep 17 13:01:09 dnsmasq[2]: started, version 2.85 DNS disabled
Sep 17 13:01:09 dnsmasq[2]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
Sep 17 13:01:09 dnsmasq-tftp[2]: TFTP root is /var/lib/
Sep 17 13:50:46 dnsmasq-tftp[2]: file /var/lib/
Sep 17 13:52:46 dnsmasq-tftp[2]: file /var/lib/
Sep 17 14:37:38 dnsmasq[2]: exiting on receipt of SIGTERM
Sep 17 14:37:39 dnsmasq[2]: started, version 2.85 DNS disabled
Sep 17 14:37:39 dnsmasq[2]: compile time options: IPv6 GNU-getopt DBus no-UBus no-i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
Sep 17 14:37:39 dnsmasq-tftp[2]: TFTP root is /var/lib/
Sep 17 14:38:41 dnsmasq-tftp[2]: file /var/lib/
Sep 17 14:42:34 dnsmasq-tftp[2]: file /var/lib/
Sep 17 14:46:31 dnsmasq-tftp[2]: file /var/lib/
```
The first section there was when ironic-inspector was booting and it seemed to request the correct file sometimes. But the latter is when doing `cleaning` and it consistently fails. Notice the additional `Iy e` for the files it looks. Creating that file does not help though.
Note:
- Running with tls-e and ironic-inspector
affects: | neutron → ironic |
More debug data, here is the tcpdump. Top one is with ironic-inspector, and bottom one that is broken is cleaning: 255.255. bootps: BOOTP/DHCP, Request from 00:25:90:d5:bf:28 (oui Unknown), length 347 0.provisioning. openstack. lab.bootps > 255.255. 255.255. bootpc: BOOTP/DHCP, Reply, length 300 255.255. bootps: BOOTP/DHCP, Request from 00:25:90:d5:bf:28 (oui Unknown), length 359 0.provisioning. openstack. lab.bootps > 255.255. 255.255. bootpc: BOOTP/DHCP, Reply, length 300 5.201.remote- as > saruman- 0.provisioning. openstack. lab.tftp: TFTP, length 41, RRQ "snponly.efi" octet tsize 0 blksize 1468 5.201.brvread > saruman- 0.provisioning. openstack. lab.tftp: TFTP, length 33, RRQ "snponly.efi" octet blksize 1468 255.255. bootps: BOOTP/DHCP, Request from 00:25:90:d5:bf:18 (oui Unknown), length 347 255.255. bootps: BOOTP/DHCP, Request from 00:25:90:d5:bf:18 (oui Unknown), length 359 5.181.imgames > saruman- 0.provisioning. openstack. lab.tftp: TFTP, length 58, RRQ "snponly. efiM-}^ DM-@M-( ^ELy^N M-)M-~M- )M-~M-@ M-(^Ed" octet tsize 0 blksize 1468 255.255. bootps: BOOTP/DHCP, Request from 00:25:90:d5:bf:28 (oui Unknown), length 391 0.provisioning. openstack. lab.bootps > 192.168. 5.201.bootpc: BOOTP/DHCP, Reply, length 328 255.255. bootps: BOOTP/DHCP, Request from 00:25:90:d5:bf:28 (oui Unknown), length 391 0.provisioning. openstack. lab.bootps > 192.168. 5.201.bootpc: BOOTP/DHCP, Reply, length 328 255.255. bootps: BOOTP/DHCP, Request from 00:25:90:d5:bf:28 (oui Unknown), length 403 0.provisioning. openstack. lab.bootps > 192.168. 5.201.bootpc: BOOTP/DHCP, Reply, length 328
```
sudo tcpdump -i vlan50 port 67 or port 68 or port 69 or port 4011
dropped privs to tcpdump
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on vlan50, link-type EN10MB (Ethernet), snapshot length 262144 bytes
02:44:22.791779 IP 0.0.0.0.bootpc > 255.255.
02:44:25.812748 IP controller-
02:44:26.646082 IP 0.0.0.0.bootpc > 255.255.
02:44:26.664178 IP controller-
02:44:26.670826 IP 192.168.
02:44:26.763110 IP 192.168.
02:44:27.592279 IP 0.0.0.0.bootpc > 255.255.
02:44:30.677202 IP 0.0.0.0.bootpc > 255.255.
02:44:30.685257 IP 192.168.
02:44:52.267802 IP 0.0.0.0.bootpc > 255.255.
02:44:52.268835 IP controller-
02:44:59.270320 IP 0.0.0.0.bootpc > 255.255.
02:44:59.271237 IP saruman-
02:45:13.331022 IP 0.0.0.0.bootpc > 255.255.
02:45:13.334344 IP controller-
```