ID: 6525
Title: Raw Edition: Graphing pages are now themed correctly
Component: Multisite
Level: 2
Class: Bug fix
Version: 1.6.0i1
The graphing pages of the Raw Edition were always rendered in the classic theme
style. The pages are now rendered in either the classic or the modern style
depending on the choose theme.
ID: 6509
Title: Pasting with automatic text splitting in list of input elements
Component: Multisite
Level: 2
Class: New feature
Version: 1.6.0i1
When a dialog is using a self extending list of input elements, like e.g. the
host- and service input fields at the bottom of the "hosts & service parameters"
rule editor, a text can be pasted into the last input field which is then split
by ";" separators. Each of the resulting parts is then added to a dedicated input
field. This is only active for the last (empty) input field.
This makes it a lot easier to populate such dialogs with a longer list of items.
ID: 6500
Title: Fixed config generation for shadow hosts/services
Component: config
Level: 2
Class: Bug fix
Version: 1.6.0i1
The Check_MK Micro Core configuration generated by "cmk -U", "cmk -O", or
"cmk -R" was broken for shadow hosts/services, leading to CMC crashes later
when the core tried to use such a configuration. This was a regression
since 1.5.0i1 and has been fixed now.
ID: 6499
Title: Fixed execution of event console actions
Component: Event Console
Level: 2
Class: Bug fix
Version: 1.6.0i1
The execution of actions defined in event console rules was broken since
1.5.0b1: Under various circumstances, the action was not executed at all,
and a Python exception was logged to var/log/mkeventd.log. This has been
fixed now.
ID: 6450
Title: Fixed handling of "SNMP" and "Dual Check_MK Agent + SNMP" tags when migrating from <1.5
Component: WATO
Level: 2
Class: Bug fix
Version: 1.6.0i1
In addition to the problem that has been fixed with #6446, the werk #5535 introduced a problem when
one has not modified the tag group "Agent type".
In this situation the "Agent type" tag group is automatically changed to the
new format (as described in #5535).
During this process two tags were not migrated correctly:
<ul>
<li>Agent type: SNMP (Networking device, Appliance) (Tag-ID: snmp-only)</li>
<li>Agent type: Dual (Dual: Check_MK Agent + SNMP) (Tag-ID: snmp-tcp)</li>
</ul>
When editing the host, the new Agent type and SNMP attributes are selected correctly and also saved
correctly. No host lost his attributes in this case. But when saving the tag list of hosts to the
config files, the tags "snmp-only" and "snmp-tcp" were not set anymore.
This is a problem because existing rules may refer to these tags.
The second part of this problem are these probably existing rules. When you open them in the GUI and
saving them to the disk again, these rules will loose their conditions, because these tags did not
exist anymore.
We have now changed the migration procedure to work like this:
<ul>
<li>In the moment you update and the old "Agent type" tag group is migrated to the new one two new
auxiliary tags are added to your configuration (snmp-only: "Legacy: SNMP ..." and snmp-tcp: "Legacy: Dual:...")</li>
<li>Now editing of existing rules will work again</li>
<li>Hosts that have "Agent type" configured to "No agent" and "SNMP" to "SNMP v2 or v3" get
have the aux tag snmp-only set</li>
<li>Hosts that have "Agent type" configured to "Contact either Check_MK Agent or use datasource program"
and "SNMP" to "SNMP v2 or v3" will have the aux tag snmp-tcp set</li>
<li>Now the rules mentioned above will match again on these hosts</li>
<li>In case you want to clean up the legacy aux tags, you can now try to delete them. The GUI will warn
you about all rules referring to them. You'll now have to clean them up.</li>
<li>"Legacy: SNMP ..." needs to be converted to "SNMP -> SNMP v2 or v3" and "Agent: No Agent"</li>
<li>"Legacy: Dual: ..." needs to be converted to "SNMP -> SNMP v2 or v3" and "Agent: Contact either Check_MK Agent or use datasource program"</li>
<li>After cleaning up all refereces, you can delete the legacy tags.</li>
<ul>
ID: 6016
Title: Fixed creation of rule-based downtimes
Component: cmc
Level: 2
Class: Bug fix
Version: 1.5.0p2
Due to a bug introduced in 1.5.0i3, it was impossible to create new working
rule-based downtimes: Although the corresponding rules seemed to work fine,
no actual downtimes were created from them, as could be seen from the
"Downtimes" view.
ID: 6446
Title: Fixed changing agent type from "No agent" to agent in some cases
Component: WATO
Level: 2
Class: Bug fix
Version: 1.6.0i1
With werk #5535 we changed the tag group "Agent type" to be a builtin tag
group. When a pre-1.5 site modified this tag group before updating to 1.5, this
tag group was left untouched.
In this situation hosts that were marked as "No agent" (ping only hosts) were
suddenly set to "Check_MK Agent (Server)" which resulted in error messages
in the monitoring after activating the configuration, because these hosts got
a Check_MK service and tried to contact the agent while there is none on the
affected hosts.
We have now changed the migration logic to extend the locally modified "Agent
type" tag group with the options Check_MK 1.5 needs. This change should make
your "No agent" hosts now stick with the intended configuration.
In case you are affected by this issue, you may notice that the choices of the
"Agent type" are now extended with some new options which may be confusing in
the first moment. You can now navigate to the "Host tags" page in WATO and edit
the tag group "agent" to sort the new options according to your needs.
The tag choices in the tag group "Agent type" that are available in your site
after the update (that are not part of the 1.5 standard) are displayed with the
"Legacy: " prefix. This can be useful in the moment you want to clean them up.
To migrate the legacy choices you need to clean up all objects referring these
choices before they can safely be removed. Examples:
<ul>
<li>The legacy "No Agent" choice was using the Tag ID "ping". The new one uses
the "no-agent" tag ID. You can now delete the legacy choice from the tag
group and hit save. The GUI will then inform you about all hosts, folders
or rulesets using this tag choice. Navigate to all objects and change the
old setting to the new one. After that you can safely remove the legacy
choice.</li>
<li>For the snmp-only, snmp-v1 and snmp-tcp options it's a bit more complicated
because it involves now two tag groups (SNMP + Agent type). To use the new
scheme you need to set the configuration like this:
<ul>
<li>snmp-only: Agent type = "No agent" and SNMP = SNMP v2 or v3</li>
<li>snmp-v1: Agent type = "No agent" and SNMP = SNMP v1</li>
<li>snmp-tcp: Agent type = "Contact either Check_MK Agent or use datasource program" and SNMP = SNMP v2 or v3</li>
</ul>
</li>
</ul>
ID: 6435
Title: omd stop on all processes of a site terminates remaining site processes
Component: Site Management
Level: 2
Class: Bug fix
Version: 1.5.0p1
When OMD stop is being performed not all processes of the site user were
stopped. The call only tried to stop the processes controlled by the init
scripts.
After a "omd stop" call for all processes of a site stopped the processes
controlled by the init scripts, OMD is now searching for remaining
(uncontrolled) site processes, e.g. still running background jobs or other
processes and sends a SIGTERM to each of them.
It waits up to 5 seconds for them to stop. In case the processes did not
finish in time, it terminates the OMD call with an exit code of 1.
ID: 6437
Title: Fixed event cancelling when no match groups are used
Component: Event Console
Level: 2
Class: Bug fix
Version: 1.6.0i1
Canceling of Event Console events using the message text was not working
correctly when using simple string matching instead of regex or mixed
types of matches (e.g. regex for the match text and string match for the
cancel text) matching.
This regression affects all previous 1.5 releases.