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
Running icingacli director config deploymentstatus returns that there currently is a failed deplyoment and exits with EXIT_CODE!=0
Current Behavior
If you have a failed deployment (that possibly prevents reloading icinga or activating new config from a kickstart) the currently is no possibilty to check for said failed deployment (at least to my knowledge).
Make the check return above expected behavior or e.g. add a parameter --failed to check for failed deployments since the last active deployment.
Another possible solution could be monitoring automatic jobs for config deployment (if you have any). But this is not a viable way at the moment because you can't monitor/check only one jobs (see #2698 and #2740)
Your Environment
Director version (System - About): 1.11.0
Icinga Web 2 version and modules (System - About): 2.12
Icinga 2 version (icinga2 --version):2.14
Operating System and version:rhel8
Webserver, PHP versions: php7.2
The text was updated successfully, but these errors were encountered:
Expected Behavior
Running
icingacli director config deploymentstatus
returns that there currently is a failed deplyoment and exits with EXIT_CODE!=0Current Behavior
If you have a failed deployment (that possibly prevents reloading icinga or activating new config from a kickstart) the currently is no possibilty to check for said failed deployment (at least to my knowledge).
Possible Solution
Make the check return above expected behavior or e.g. add a parameter --failed to check for failed deployments since the last active deployment.
Another possible solution could be monitoring automatic jobs for config deployment (if you have any). But this is not a viable way at the moment because you can't monitor/check only one jobs (see #2698 and #2740)
Your Environment
icinga2 --version
):2.14The text was updated successfully, but these errors were encountered: