[Starlingx-discuss] PXE-boot error with 5.0 build
Hi, We are trying to bring-up Starlingx in ALL-IN-ONE DUPLEX mode and using the 5.0 release-build. The first node is coming up properly but the second node is failed in PXE boot. Note: We have created OAM and MGMT VLAN over same interface and enable the pxeboot on the interface. This networking was working fine with starlingx:4.0 and we are seeing the issue with 5.0 only The screen-shot is attached for your reference. Thanks, Ankush
The error in your screenshot indicates trouble retrieving the initrd. I would check the dnsmasq logs in daemon.log on the active controller. You'll see the DHCP request and response there, and should see tftp requests for the pxelinux.cfg file, followed by the bzImage (kernel) and initrd. In my test, the initrd is the last of the three files, so it's surprising there'd be an issue on that one and not the earlier files. Maybe the logs will shed some light for you. Example from my system: [sysadmin@controller-0 ~(keystone_admin)]$ tail -f /var/log/daemon.log | grep dnsmasq 2021-06-16T14:40:21.000 controller-0 dnsmasq-dhcp[101586]: info DHCPDISCOVER(enp0s8) 08:00:27:2a:b1:e7 2021-06-16T14:40:21.000 controller-0 dnsmasq-dhcp[101586]: info DHCPOFFER(enp0s8) 192.168.204.3 08:00:27:2a:b1:e7 2021-06-16T14:40:23.000 controller-0 dnsmasq-dhcp[101586]: info DHCPREQUEST(enp0s8) 192.168.204.3 08:00:27:2a:b1:e7 2021-06-16T14:40:23.000 controller-0 dnsmasq-dhcp[101586]: info DHCPACK(enp0s8) 192.168.204.3 08:00:27:2a:b1:e7 controller-1 2021-06-16T14:40:23.000 controller-0 dnsmasq-tftp[101586]: err error 0 TFTP Aborted received from 192.168.204.3 2021-06-16T14:40:23.000 controller-0 dnsmasq-tftp[101586]: info failed sending /pxeboot/pxelinux.0 to 192.168.204.3 2021-06-16T14:40:23.000 controller-0 dnsmasq-tftp[101586]: info sent /pxeboot/pxelinux.0 to 192.168.204.3 2021-06-16T14:40:23.000 controller-0 dnsmasq-tftp[101586]: err file /pxeboot/pxelinux.cfg/ecf77d23-7792-4e4f-95bc-46a4d0ca2b36 not found 2021-06-16T14:40:23.000 controller-0 dnsmasq-tftp[101586]: info sent /pxeboot/pxelinux.cfg/01-08-00-27-2a-b1-e7 to 192.168.204.3 2021-06-16T14:40:23.000 controller-0 dnsmasq-tftp[101586]: info sent /pxeboot/menu.c32 to 192.168.204.3 2021-06-16T14:40:23.000 controller-0 dnsmasq-tftp[101586]: info sent /pxeboot/pxelinux.cfg/01-08-00-27-2a-b1-e7 to 192.168.204.3 2021-06-16T14:40:25.000 controller-0 dnsmasq-script[101586]: debug sysinv 2021-06-16 14:40:25.373 2363971 INFO sysinv.cmd.dnsmasq_lease_update [-] Called 'add' for mac '08:00:27:2a:b1:e7' with ip '192.168.204.3' 2021-06-16T14:40:25.000 controller-0 dnsmasq-script[101586]: debug sysinv 2021-06-16 14:40:25.565 2363971 INFO sysinv.openstack.common.rpc.common [-] Connected to AMQP server on 192.168.204.1:5672 2021-06-16T14:40:30.000 controller-0 dnsmasq-tftp[101586]: info sent /pxeboot/rel-21.05/installer-bzImage to 192.168.204.3 2021-06-16T14:40:39.000 controller-0 dnsmasq-tftp[101586]: info sent /pxeboot/rel-21.05/installer-initrd to 192.168.204.3 2021-06-16T14:40:57.000 controller-0 dnsmasq-dhcp[101586]: info DHCPDISCOVER(enp0s8) 08:00:27:2a:b1:e7 2021-06-16T14:40:57.000 controller-0 dnsmasq-dhcp[101586]: info DHCPOFFER(enp0s8) 192.168.204.3 08:00:27:2a:b1:e7 2021-06-16T14:40:57.000 controller-0 dnsmasq-dhcp[101586]: info DHCPREQUEST(enp0s8) 192.168.204.3 08:00:27:2a:b1:e7 2021-06-16T14:40:57.000 controller-0 dnsmasq-dhcp[101586]: info DHCPACK(enp0s8) 192.168.204.3 08:00:27:2a:b1:e7 controller-1 From: Rai, Ankush <Ankush.Rai@commscope.com> Sent: Tuesday, June 15, 2021 2:14 PM To: starlingx-discuss@lists.starlingx.io Cc: Sambandan, Devaraj <Devaraj.Sambandan@commscope.com>; Dharwadkar, Sriram <Sriram.Dharwadkar@commscope.com> Subject: [Starlingx-discuss] PXE-boot error with 5.0 build [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, We are trying to bring-up Starlingx in ALL-IN-ONE DUPLEX mode and using the 5.0 release-build. The first node is coming up properly but the second node is failed in PXE boot. Note: We have created OAM and MGMT VLAN over same interface and enable the pxeboot on the interface. This networking was working fine with starlingx:4.0 and we are seeing the issue with 5.0 only The screen-shot is attached for your reference. Thanks, Ankush
participants (2)
-
Penney, Don
-
Rai, Ankush