Is there a way to move a service to undecided with the ansible collection?
When a certain automated maintenance is performed on some servers, it causes a specific plugin to go unknown and not recover. If you move the service to undecided, activate then do a discovery, re-add it and activate it goes back to normal. This can be automated with the ansible collection by doing a tabula_rasa on the host with the discovery module but I am not sure if doing a full tabula rasa is necessary if I can restrict it to the problem service. Another option could be doing it from the command line with âcmk -vII --detect-plugins=df myserver01â but would prefer via the api/ansible collection if possible. I note that it says the tabula_rasa function wont work with 2.4, we wont be upgrading for a while so have not investigated this or how we would achieve the equivalent, I will cross that bridge when I come to it.
Hi for more context, its the DR:BD plugin. I am told by the support team for the servers, its when they do some sort of site swap in the background, I am guessing the plugin detects an error of some sort when they are performing their site swap and the only way to reset the error they have found was to set it to undecided and then re-add it. I am told they can do this currently via the api (we are running 2.0) and we are planning our upgrade to 2.3 but their old api automation does not work in 2.3 so they are trying to reproduce their automation with the ansible collection. I do see there is werk #14631 for the plugin, but I wont know if that changes anything for us until our upgrade is completed.