Actions
Feature #4772
closed
Display better error messages for DHCP errors
Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
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?
Updated by Dominic Cleal about 10 years ago
- Related to Feature #1966: Improve UI errors when smart proxy returns 400 bad request added
Updated by Dominic Cleal about 10 years ago
- Status changed from New to Feedback
Have a look at #1966, we're improving the UI errors to explain that the "400 Bad Request" actually came from a proxy and the identity of the proxy. The bit we don't have at the moment is getting the underlying reason from the proxy into the proxy's HTTP response so Foreman can consume it.
Updated by Dominic Cleal over 9 years ago
- Related to Feature #7916: Foreman WebUI should give clearer error message when foreman-proxy cannot be contacted added
Actions