Actions
Bug #947
open
Foreman UI doesn't report omapi_key error properly
Status:
New
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
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
Updated by Mikael Fridh about 13 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.
Updated by Ohad Levy almost 9 years ago
- Description updated (diff)
- Assignee set to Anonymous
Dmitri - is this still correct after the refactoring ?
Updated by Lukas Zapletal over 3 years ago
This is how it looks like when a key is not valid:
$ omshell > key fldskjfdslkj dGVzdAo= > server localhost > connect dhcpctl_connect: no more
We should catch this error.
Updated by Anna Vítová over 3 years ago
- Assignee changed from Anonymous to Anna Vítová
Updated by Lukas Zapletal over 3 years ago
- Project changed from Smart Proxy to Foreman
- Category changed from DHCP to DHCP
- Triaged changed from No to Yes
This appears to be correct on the proxy and needs to be fixed in Foreman core.
Actions