Project

General

Profile

Actions

Bug #947

open

Foreman UI doesn't report omapi_key error properly

Added by Marcello de Sousa over 13 years ago. Updated about 3 years ago.

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

Description

If the omapi_key is incorrect (I forced an incorrect key) Foreman's interface is not reporting the error.
In the proxy.log (in debug mode) I can see the error:

(...)
E, [2011-05-03T17:51:57.835019 #10819] ERROR -- : Omshell failed:
> > > obj: <null>
, > obj: host
, > obj: host
, hardware-address = 00:0c:29:38:71:62
, > can't open object: connection reset by peer
, obj: host
, hardware-address = 00:0c:29:38:71:62
, > can't destroy object: not connected
, obj: host
, hardware-address = 00:0c:29:38:71:62
, >
E, [2011-05-03T17:51:57.835393 #10819] ERROR -- : Failed to remove DHCP reservation for  => 192.168.115.156 / 00:0c:29:38:71:62: No response from DHCP


Related issues 2 (0 open2 closed)

Related to Smart Proxy - Bug #853: If used with the proxy, the dhcpd server is open for connections from any serverClosedOhad Levy04/18/2011Actions
Related to Smart Proxy - Bug #1366: key conflict from omshell are not reportedClosedMikael Fridh12/04/2011Actions
Actions

Also available in: Atom PDF