Closed K0nne closed 3 years ago
Thanks for the bugfix. Unfortunately it doen't work as expected. It solves the initial problem by returning:
[UNKNOWN]: Icinga Custom Error was thrown: Custom Exception: OK
Custom exception occured:
Everything is fine.
Unfortunately the checks stay in this state, even if the HyperV ressources are present. After I switched back to the current master, the checks went [OK] again.
Hi, thanks that you have tested it but the PR is not ready.
Hello,
when a HyperV host is running "empty", because all of its VMs, snapshots etc. have been moved on purpose, the checks for Overcommitment, VM Health and Snapshots are returning the following unknown message:
Is it possible to detect this case and still return an OK?