Project

General

Profile

Bug #947

Foreman UI doesn't report omapi_key error properly

Added by Marcello de Sousa over 9 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Normal
Assignee:
Dmitri Dolguikh
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
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

Related to Smart Proxy - Bug #853: If used with the proxy, the dhcpd server is open for connections from any serverClosed2011-04-18
Related to Smart Proxy - Bug #1366: key conflict from omshell are not reportedClosed2011-12-04

History

#1 Updated by Ohad Levy about 9 years ago

  • Target version changed from 0.3 to 1.0

#2 Updated by Mikael Fridh about 9 years ago

Looks similar to this pull request:
https://github.com/theforeman/smart-proxy/pull/9

Basically, need to regex match some more of the omshell errors.

#3 Updated by Ohad Levy over 8 years ago

  • Target version deleted (1.0)

#4 Updated by Ohad Levy almost 5 years ago

  • Description updated (diff)
  • Assignee set to Dmitri Dolguikh

Dmitri - is this still correct after the refactoring ?

Also available in: Atom PDF