Closed ValkyrieOps closed 3 years ago
Thanks for reporting this.
In most other places I am using chef still I also manage the systemd unit file (which we don't here if I am not mistaken) so when I use the following resource: https://docs.chef.io/resources/systemd_unit/ to create the unit it knows how to handle that for you.
I have not tested this: I think what we would want to do here is define it with an action of :nothing
(and no content) to put it in our resource collection to be called later. Then use a notification to reload the unit file configuration before the service restart is called. Let me know if you want any pointers on taking a stab at this, otherwise I will try to get to it when I can. I am sure we are running into this org and we didn't notice the warning.
Hey no worries, appreciate you getting back to me. Your suggested fix seems like the way to go, hopefully this coming week I can sit down and try to implement the changes. Will keep you posted on progress. Thanks!
Chef Version
Chef: 16.6.4 CentOS 7.6.1810
Input
A stripped down resource to deploy the agent while specifying which version to install
Output
Impact
Tiny. I have added an execute statement to the agent resource locally for now
Expected Behavior
I would think that after running an upgrade the systemd daemon would get reloaded
Actual Behavior
Requires user to execute
systemctl daemon-reload
Steps to Reproduce your problem