You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is caused by the handler type taking a hash for the socket attribute. Due to the non-deterministic ordering of the hash retrieval you see frequent 'changes' where no actual change occurs. This causes the puppet enterprise dashboard to permanently list the node as recently changed.
This should be fixable by sorting the socket hash before using it within the json.
The text was updated successfully, but these errors were encountered:
Notice: /Stage[main]/role_sensu::Server/Sensu::Handler[relay]/Sensu_handler[relay]/socket: socket changed {'port' => '2003', 'socket' => 'carbon.hostedgraphite.com'} to '{"socket"=>"carbon.hostedgraphite.com", "port"=>2003}'
I believe this is caused by the handler type taking a hash for the socket attribute. Due to the non-deterministic ordering of the hash retrieval you see frequent 'changes' where no actual change occurs. This causes the puppet enterprise dashboard to permanently list the node as recently changed.
This should be fixable by sorting the socket hash before using it within the json.
The text was updated successfully, but these errors were encountered: