This plugin uses officialy built zabbix packages, please see https://git.openstack.org/cgit/openstack/fuel-plugin-external-zabbix/tree/pre_build_hook?h=refs/heads/master. These packages are built for Ubuntu Trusty and do use old LSB init system which doesn't support respawn. To introduce the respawn logic in zabbix agent we either have to fork zabbix and develop an upstart init script for it or upgrade the zabbix version used in plugin to a new major one. The both ways bring in a lot of extensive development and testing, which is prohibited by the maintenance policy. Also we see the fact that the issue is triggered manually and we have no information about its occurrence due to natural reasons (i.e. the app has crashed).
This plugin uses officialy built zabbix packages, please see https:/ /git.openstack. org/cgit/ openstack/ fuel-plugin- external- zabbix/ tree/pre_ build_hook? h=refs/ heads/master. These packages are built for Ubuntu Trusty and do use old LSB init system which doesn't support respawn. To introduce the respawn logic in zabbix agent we either have to fork zabbix and develop an upstart init script for it or upgrade the zabbix version used in plugin to a new major one. The both ways bring in a lot of extensive development and testing, which is prohibited by the maintenance policy. Also we see the fact that the issue is triggered manually and we have no information about its occurrence due to natural reasons (i.e. the app has crashed).
Given all the above I am moving it to Won't Fix.