You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is hardly an issue with Icinga Web. The result you get is what Web gets from Icinga's API.
I don't know what the issue is, but it seems to me that some of the hosts in the group are not found, and some are. Or that some of the hosts have no downtime, but some have.
K0nne
changed the title
Usage of IcingaWeb2 api commands returns 404, but is successful
Usage of IcingaWeb2 api command returns 404, but is successful
Feb 8, 2024
Describe the bug
When I use the icingaweb2 api, some commands return a 404, but the commands are successful executed.
To Reproduce
IcingaWeb2 2.9.6
returns:
{"status":"error","message":"fqdn master1: Can't send external Icinga command: 404 No objects found.\nfqdn master2: Can't send external Icinga command: 404 No objects found."}
IcingaWeb2 2.12.1
Interestingly it works for single services with
?host=<hostname>&service=<servicename>
returns:
{"status":"error","message":"fqdn master1: Can't send external Icinga command: 404 No objects found.\nfqdn master2: Can't send external Icinga command: 404 No objects found."}
Expected behavior
Successful execution should be reflected as such.
Your Environment
Include as many relevant details about the environment you experienced the problem in
icinga2 --version
): 2.13.9php --version
):RHEL7 with Icingaweb2 2.9.6:
RHEL8 with IcingaWeb2 2.12.1:
Additional context
icingaweb2 --> icinga:
permissions = [ "status/query", "actions/*", "objects/modify/*", "objects/query/*", ]
WebUser permissions are the same in 2.9.6 and 2.12.1:
The text was updated successfully, but these errors were encountered: