Please try to fill out as much of the information below as you can. Thank you!
Which version contains the bug?
No response
Description
The "Restart Kibana" handler in roles/kibana/handlers/main.yml only checks
not kibana_freshstart.changed. Unlike the logstash and beats restart handlers, it does
not also check kibana_enable.
As a result, if kibana_enable: false (Kibana should not run) but the role still changes
kibana.yml (kibana_manage_yaml is true by default), the config task notifies the
handler and it tries to restart the kibana service anyway — contrary to the user having
disabled it.
Fix
Guard the handler with kibana_enable as well, matching the logstash/beats handlers:
when:
- kibana_enable | bool
- not kibana_freshstart.changed | bool
Please try to fill out as much of the information below as you can. Thank you!
Which version contains the bug?
No response
Description
The "Restart Kibana" handler in
roles/kibana/handlers/main.ymlonly checksnot kibana_freshstart.changed. Unlike the logstash and beats restart handlers, it doesnot also check
kibana_enable.As a result, if
kibana_enable: false(Kibana should not run) but the role still changeskibana.yml(kibana_manage_yamlistrueby default), the config task notifies thehandler and it tries to restart the kibana service anyway — contrary to the user having
disabled it.
Fix
Guard the handler with
kibana_enableas well, matching the logstash/beats handlers: