![]() Oct 22 09:50:05 sc-ironic04 in.tftpd: remap: rule 2: exit Oct 22 09:50:04 sc-ironic04 in.tftpd: RRQ from 10.33.23.94 filename grub圆4.efi remapped to /tftpboot/grub圆4.efi Oct 22 09:50:04 sc-ironic04 in.tftpd: remap: rule 3: rewrite: /tftpboot/grub圆4.efi ![]() Oct 22 09:50:04 sc-ironic04 in.tftpd: RRQ from 10.33.23.94 filename boot圆4.efi remapped to /tftpboot/boot圆4.efi Oct 22 09:50:04 sc-ironic04 in.tftpd: remap: rule 3: exit Oct 22 09:50:04 sc-ironic04 in.tftpd: remap: rule 3: rewrite: /tftpboot/boot圆4.efi Oct 22 09:50:04 sc-ironic04 in.tftpd: Error code 8: User aborted the transfer Oct 22 09:50:03 sc-ironic04 in.tftpd: RRQ from 10.33.23.94 filename boot圆4.efi remapped to /tftpboot/boot圆4.efi ![]() Oct 22 09:50:03 sc-ironic04 in.tftpd: remap: rule 3: exit Oct 22 09:50:03 sc-ironic04 in.tftpd: remap: rule 3: rewrite: /tftpboot/boot圆4.efi Package tftpd is not tftp-hpa-5.2]# rpm -q tftp-hpa-5.2]# I've downloaded the relevant packages for xinetd and tftp-server and cannot find the keywords "Client" or "timed out" anywhere in the source tftp-hpa-5.2]# rpm -q tftp-hpa-5.2]# rpm -q tftpd Immediately after printing that message the tftpd (tftp-server) says client timed out. The server also says that the client successfully downloaded the last file (deploy_ramdisk). Obviously the PXE client can access and does access successfully several files from the tftp server. I have traced the issue down to the tftpd (tftp-server) process on the ironic conductor which says the tftp client (PXE boot) timed out (see last log at the bottom). Occasionally I see some issues with a server not being able to deploy properly. We have over a relatively stable Openstack ironic cluster over over 300 nodes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |