Closed julian7 closed 7 years ago
Hi @julian7, thanks for opening this issue. I think this is an condition that needs to be addressed outside the cookbook. I've amended the changelog in #550 to more explicitly describe this potential condition as an important upgrade consideration.
When you upgrade from 0.26.5 to a higher version on a systemd-capable linux (ubuntu xenial tested), the upgrade doesn't stop old services, therefore new services will never start.
Expected Behavior
Upgrade happens automatically, with no manual intervention required. SystemV services are stopped before upgrade (maybe the correct behavior belongs to sensu project instead, and systemd setups would kill rogue processes before starting)
Current Behavior
Old processes linger, leaving systemd units in activating state:
Possible Solution
I think of two possible resolutions of the problem:
Steps to Reproduce (for bugs)
Your Environment