sensu / sensu-go

Simple. Scalable. Multi-cloud monitoring.
https://sensu.io
MIT License
1.03k stars 175 forks source link

Check command changes not picked up by agents #3160

Closed ITStreet66 closed 5 years ago

ITStreet66 commented 5 years ago

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)

  1. Make a change to an existing check like updating the command it runs
  2. Schedule an ad-hoc run of that check on an agent subscribed to the check
  3. 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

ITStreet66 commented 5 years ago

Closing this as this was caused by a bug that was fixed in 5.11.x as this was a consequence of high CPU utilization caused by watcher.