Werk 16625 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: service_discovery/bulk_discovery: reformulate documentation for mode option
Class: fix
Compatible: compat
Component: rest-api
Date: 1710239567
Edition: cre
Level: 1
Version: 2.2.0p25
Previously, the single service discovery and the bulk discovery shared the same
documentation for the mode field. This covers the use cases for the bulk discovery
to a certain degree. This werk fixes this. In addition, this werk also
resolves previously non working modes 'fix_all' and 'tabula_rasa'.
------------------------------------<diff>-------------------------------------------
Title: service_discovery/bulk_discovery: reformulate documentation for mode option
Class: fix
Compatible: compat
Component: rest-api
Date: 1710239567
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
Previously, the single service discovery and the bulk discovery shared the same
documentation for the mode field. This covers the use cases for the bulk discovery
to a certain degree. This werk fixes this. In addition, this werk also
resolves previously non working modes 'fix_all' and 'tabula_rasa'.
Werk 16549 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Agent updates failing on Solaris 10
Class: fix
Compatible: incomp
Component: agents
Date: 1709282638
Edition: cee
Level: 1
Version: 2.2.0p25
On some Solaris 10 systems, an agent update did crash with error message
C+:
/var/sadm/pkg/check-mk-agent/install/postremove: syntax error at line 19: `(' unexpected
pkgrm: ERROR: postremove script did not complete successfully
C-:
If you ran into this error, to make the update perform again, please delete the file
<code>/var/sadm/pkg/check-mk-agent/install/postremove</code> on affected systems.
Technical background:\
The postremove script used the subshell evaluation syntax <code>$(...)</code> that is incompatible to the standard <code>bin/sh</code> shell found on some Solaris 10 systems.
------------------------------------<diff>-------------------------------------------
Title: Agent updates failing on Solaris 10
Class: fix
Compatible: incomp
Component: agents
Date: 1709282638
Edition: cee
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
On some Solaris 10 systems, an agent update did crash with error message
C+:
/var/sadm/pkg/check-mk-agent/install/postremove: syntax error at line 19: `(' unexpected
pkgrm: ERROR: postremove script did not complete successfully
C-:
If you ran into this error, to make the update perform again, please delete the file
<code>/var/sadm/pkg/check-mk-agent/install/postremove</code> on affected systems.
Technical background:\
The postremove script used the subshell evaluation syntax <code>$(...)</code> that is incompatible to the standard <code>bin/sh</code> shell found on some Solaris 10 systems.
Werk 16495 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: check_mailboxes: fix check of multiple mailboxes
Class: fix
Compatible: compat
Component: checks
Date: 1709557446
Edition: cre
Level: 1
Version: 2.2.0p25
When selecting to check multiple mailboxes, the software always checked only the last specified mailbox.
This werk fixes this behaviour.
------------------------------------<diff>-------------------------------------------
Title: check_mailboxes: fix check of multiple mailboxes
Class: fix
Compatible: compat
Component: checks
Date: 1709557446
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
When selecting to check multiple mailboxes, the software always checked only the last specified mailbox.
This werk fixes this behaviour.
Werk 16599 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: jolokia metrics: restores 'default product' behavior
Class: fix
Compatible: compat
Component: checks
Date: 1710165014
Edition: cre
Level: 1
Version: 2.2.0p25
The check plugin no longer showed any metrics if a product was not specified in the ruleset configuration.
This werk restores the original behaviour, using as a default product the one reported in the info section of the agent output.
------------------------------------<diff>-------------------------------------------
Title: jolokia metrics: restores 'default product' behavior
Class: fix
Compatible: compat
Component: checks
Date: 1710165014
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
The check plugin no longer showed any metrics if a product was not specified in the ruleset configuration.
This werk restores the original behaviour, using as a default product the one reported in the info section of the agent output.
Werk 16630 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Prevent check_mail crash for "Move to subfolder" option
Class: fix
Compatible: compat
Component: checks
Date: 1710753543
Edition: cre
Level: 1
Version: 2.2.0p25
The active check check_mail can be configured to move mail messages from the inbox to a subfolder via the options "Forward mails as events to Event Console" > "Cleanup messages" > "Move to subfolder".
For IMAP the copying of mails crashed when there were no mails available in the inbox.
This is fixed to skipping the copy command in case there are no mails given.
------------------------------------<diff>-------------------------------------------
Title: Prevent check_mail crash for "Move to subfolder" option
Class: fix
Compatible: compat
Component: checks
Date: 1710753543
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
The active check check_mail can be configured to move mail messages from the inbox to a subfolder via the options "Forward mails as events to Event Console" > "Cleanup messages" > "Move to subfolder".
For IMAP the copying of mails crashed when there were no mails available in the inbox.
This is fixed to skipping the copy command in case there are no mails given.
Werk 16485 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: host_config: Create hosts in folder with umlauts
Class: fix
Compatible: compat
Component: rest-api
Date: 1710161510
Edition: cre
Level: 1
Version: 2.2.0p25
When creating hosts in a folder with umlauts in the name via one of the
<code>host_config</code> endpoints the endpoint would return an error 400 even though
the query was correct.
Now the hosts are created correctly.
------------------------------------<diff>-------------------------------------------
Title: host_config: Create hosts in folder with umlauts
Class: fix
Compatible: compat
Component: rest-api
Date: 1710161510
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
When creating hosts in a folder with umlauts in the name via one of the
<code>host_config</code> endpoints the endpoint would return an error 400 even though
the query was correct.
Now the hosts are created correctly.
Werk 16496 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: agent_azure: fix parsing loadbalancer data
Class: fix
Compatible: compat
Component: checks
Date: 1709739981
Edition: cre
Level: 1
Version: 2.2.0p25
The agent would crash if information (backend pools or outbound rules) was missing for a load balancer.
This werk ensures that the system handles scenarios where this data may not be present.
------------------------------------<diff>-------------------------------------------
Title: agent_azure: fix parsing loadbalancer data
Class: fix
Compatible: compat
Component: checks
Date: 1709739981
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
The agent would crash if information (backend pools or outbound rules) was missing for a load balancer.
This werk ensures that the system handles scenarios where this data may not be present.
Werk 16609 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Publish permission handling for various components
Class: fix
Compatible: incomp
Component: multisite
Date: 1710410065
Edition: cre
Level: 1
Version: 2.2.0p25
Werk 13498 introduced the possibility to set limit publish permissions
to certain contact groups, sites etc. Still, the permission "Publish views"
(e.g. for publishing views) was needed to see the published views. With
Werk 16320 this has been fixed for dashboards, views and reports.
This werk fixes the behavior for the remaining components (Bookmarks, Graphs,
SLAs and Reports).
Note: Please check the respective publish configuration.
------------------------------------<diff>-------------------------------------------
Title: Publish permission handling for various components
Class: fix
Compatible: incomp
Component: multisite
Date: 1710410065
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
Werk 13498 introduced the possibility to set limit publish permissions
to certain contact groups, sites etc. Still, the permission "Publish views"
(e.g. for publishing views) was needed to see the published views. With
Werk 16320 this has been fixed for dashboards, views and reports.
This werk fixes the behavior for the remaining components (Bookmarks, Graphs,
SLAs and Reports).
Note: Please check the respective publish configuration.
Werk 16508 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Make LDAP connection test errors more explicit
Class: feature
Compatible: compat
Component: wato
Date: 1709829281
Edition: cre
Level: 1
Version: 2.2.0p25
The LDAP connection test does not give enough information
about which DN configured results in an error.
This werk adds identifying information for the DN to the
error message to make it easier to identify the problem.
------------------------------------<diff>-------------------------------------------
Title: Make LDAP connection test errors more explicit
Class: feature
Compatible: compat
Component: wato
Date: 1709829281
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
The LDAP connection test does not give enough information
about which DN configured results in an error.
This werk adds identifying information for the DN to the
error message to make it easier to identify the problem.
Werk 16582 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: passwords: Fix internal server error when creating a password in CME with a non existent customer
Class: fix
Compatible: compat
Component: rest-api
Date: 1710234772
Edition: cre
Level: 1
Version: 2.2.0p25
Previous this Werk, a status code 500 (Internal server error) was raised when creating a password with a non existent customer. This werk fixes that and now it returns a status code 400 (Bad request) with proper informaiton about the error
------------------------------------<diff>-------------------------------------------
Title: passwords: Fix internal server error when creating a password in CME with a non existent customer
Class: fix
Compatible: compat
Component: rest-api
Date: 1710234772
Edition: cre
Level: 1
- Version: 2.2.0p24
? ^
+ Version: 2.2.0p25
? ^
Previous this Werk, a status code 500 (Internal server error) was raised when creating a password with a non existent customer. This werk fixes that and now it returns a status code 400 (Bad request) with proper informaiton about the error