When an update is made to an existing check's command I expect agents to execute the updated command configuration.
Current Behavior
The check itself in the Sensu dashboard carries the updated configuration. However, running an ad hoc check on an Agent that is subscribed to the check runs with the previous configuration of the command pre change.
Steps to Reproduce (for bugs)
Make a change to an existing check like updating the command it runs
Schedule an ad-hoc run of that check on an agent subscribed to the check
Output of the check will show it still runs with the old command. Verify this by expanding check configuration summary on the event itself and you will see it still has the old configuration
Context
Trying to test and get running sudo based checks. However, just by virtue of trying to test commands through the sensu-agent, this issue makes it so changes aren't being propagated correctly.
Your Environment
Sensu version used (sensuctl, sensu-backend, and/or sensu-agent): sensu-backend:5.10.1 sensu-agent:5.10.1
Installation method (packages, binaries, docker etc.): Installation through the Sensu Puppet module
Operating System and version (e.g. Ubuntu 14.04): CentOS 7.
Expected Behavior
When an update is made to an existing check's command I expect agents to execute the updated command configuration.
Current Behavior
The check itself in the Sensu dashboard carries the updated configuration. However, running an ad hoc check on an Agent that is subscribed to the check runs with the previous configuration of the command pre change.
Steps to Reproduce (for bugs)
Context
Trying to test and get running sudo based checks. However, just by virtue of trying to test commands through the sensu-agent, this issue makes it so changes aren't being propagated correctly.
Your Environment