Disabling and re-enabling cluster resource monitor causes custom settings to be lost
Issue
- If a cluster resource monitor has a custom setting e.g. non-default timeout value, then disabling and re-enabling the monitor causes this setting to be lost.
Environment
- Red Hat Enterprise Linux 7 (with the High Availability Add-on)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
