Project

General

Profile

Actions

Bug #11067

closed

Failing TFTP fetch filed doesn't trigger error in UI

Added by Jon Skarpeteig almost 9 years ago. Updated almost 9 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
TFTP
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

foreman-proxy.log

127.0.0.1 - - [09/Jul/2015 14:39:35] "POST /tftp/syslinux/00:50:56:bb:5e:30 HTTP/1.1" 200 - 0.0050
127.0.0.1 - - [09/Jul/2015 14:39:35] "POST /tftp/fetch_boot_file HTTP/1.1" 200 - 0.0023
127.0.0.1 - - [09/Jul/2015 14:39:35] "POST /tftp/fetch_boot_file HTTP/1.1" 200 - 0.0025
E, [2015-07-09T14:39:45.666405 #18982] ERROR -- : [31543] wget: unable to resolve host address âmirror.centos.orgâ

E, [2015-07-09T14:39:45.774575 #18982] ERROR -- : [31551] wget: unable to resolve host address âmirror.centos.orgâ

However, the build continues - failing the PXE boot step due to initrd.img and vmlinuz files being 0 byte


Related issues 1 (1 open0 closed)

Is duplicate of Smart Proxy - Feature #3034: TFTP file download should be synchronous and handle errorsNewActions
Actions #1

Updated by Dominic Cleal almost 9 years ago

  • Is duplicate of Feature #3034: TFTP file download should be synchronous and handle errors added
Actions #2

Updated by Dominic Cleal almost 9 years ago

  • Status changed from New to Duplicate

Thanks for the report, this is tracked under #3034.

Actions

Also available in: Atom PDF