ID: 13478
Title: Mitigate wrong converion of disabled service rules on update
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
During <tt>cmk-update-config</tt> some disabled services rules are being
broken by introducing an undesired escaping.
This werk reduces the number of cases in which this happens.
Users "Disabled Services" rules were affected if they fullfilled
<b>all</b> of the following criteria:
<ul>
<li>They have exactly one host condition (explicit or pattern)</li>
<li>They have no tag based conditions</li>
<li>All their patterns for the service name end in
"<tt>$</tt>"</li>
</ul>
After this werk, only rules will be affected if they additionally
<ul>
<li> have exactly one <b>explicit</b> host condition (not a regular
expression)</li>
<li> contain <b>both</b> quoted and unquoted special
characters</li> in their service name pattern
</ul>
For instance: "<tt>Foo[12]$</tt>" and
"<tt>Foo\[12\]$</tt>" will remain unchanged, whereas
"<tt>Foo\[1\][2]$</tt>" will be changed to
"<tt>Foo\[1\]\[2\]$</tt>".
If this still affects you, you can avoid meeting the above criteria.
For instance try to replace "<tt>my_hostname</tt>" by
"<tt>~^my_hostname$</tt>" or to craft a service name pattern that
does not require the trailing "<tt>$</tt>".