Project

General

Profile

Actions

Feature #4772

closed

Display better error messages for DHCP errors

Added by Josh Baird over 10 years ago. Updated over 10 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When submitting a new host with a subnet that is defined in Foreman, but not in the DHCP server's dhcpd.conf, the error that is displayed is:

Unable to save
Create DHCP Settings for pspr-d1db01.blah.com task failed with the following error: 400 Bad Request

The proxy log reveals the real problem:
E, [2014-03-21T10:22:00.509884 #20117] ERROR -- : No Subnet detected for: "172.26.92.0"

Can this error be displayed to the user in the UI?


Related issues 2 (1 open1 closed)

Related to Foreman - Feature #1966: Improve UI errors when smart proxy returns 400 bad requestClosedLukas Zapletal11/22/2012Actions
Related to Foreman - Feature #7916: Foreman WebUI should give clearer error message when foreman-proxy cannot be contactedNew10/13/2014Actions
Actions

Also available in: Atom PDF