ID: 15728
Title: mk_oracle: revert werk 15210
Component: Setup
Level: 1
Class: Bug fix
Version: 2.3.0b1
The introduction of werk 15210 brought convenience for some, while
it unintentionally broke the rules for others. This new werk reverts
the rule set back to the previous behaviour. Users should reverify
the auth values for host and port in their existing rules and
disable those options if this was previously the case.
ID: 14197
Title: BI sample configuration: fixed missing filesystems due to incorrectly used placeholder
Component: BI
Level: 1
Class: Bug fix
Version: 2.1.0p28
ID: 15726
Title: service: make service description query parameter required for 'Show the monitored service of a host' endpoint
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Prior to this werk, the service description query parameter was optional for the
'Show the monitored service of a host' endpoint. However, omitting this parameter
led to a Internal Server Error. This werk fixes this issue by making the parameter
required.
ID: 15471
Title: check_bi_aggr: Fix downtime tracking
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Until now, downtime tracking was possible only for BI aggregations
named "Aggr Host {HOSTNAME}"
With this werk downtime tracking is possible for all BI aggregations.
ID: 15610
Title: Fix <tt>Error in LIVESTATUS_TCP_ONLY_FROM</tt> during <tt>omd config</tt>
Component: Site Management
Level: 2
Class: Bug fix
Version: 2.2.0b7
If a user ran the command <tt>omd config</tt> and selected <tt>Distributed Monitoring >
LIVESTATUS_TCP_ONLY_FROM</tt>, then the following error was shown
C+:
Error in LIVESTATUS_TCP_ONLY_FROM
C-:
With this Werk, the error no longer occurs.
ID: 15607
Title: Reduce occurences of Missing data
Component: Setup
Level: 2
Class: Bug fix
Version: 2.3.0b1
The Check_MK service often showed the message
C+:
[piggyback] Missing data WARN
C-:
before a piggyback host was deleted. This lead to many false alarms in dynamic environments such as
Kubernetes. The root cause of this was that the <tt>delete-hosts</tt> automation would delete
piggyback files, which where still in use. With this Werk, the piggyback files are cleaned up by
Check_MK's dedicated housekeeping job (see Werk 5538).
ID: 15608
Title: Show explanation message instead of KeyError: 'extensions'
Component: Dynamic host configuration
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously, if a folder is moved or deleted, which is in use by a DCD connection, the following
error was shown.
C+:
09:37:31 ERROR An exception occured
Traceback (most recent call last):
File "/omd/sites/heute/lib/python3/cmk/cee/dcd/connectors/piggyback.py", line 260, in _execute_phase2
created_host_names = self._create_new_hosts(hosts_to_create)
File "/omd/sites/heute/lib/python3/cmk/cee/dcd/connectors/piggyback.py", line 479, in _create_new_hosts
created_host_names = self._create_piggyback_hosts(hosts_to_create)
File "/omd/sites/heute/lib/python3/cmk/cee/dcd/connectors/piggyback.py", line 504, in _create_piggyback_hosts
assert_never(result)
File "/omd/sites/heute/lib/python3.11/typing.py", line 2462, in assert_never
raise AssertionError(f"Expected code to be unreachable, but got: {value}")
AssertionError: Expected code to be unreachable, but got: None
C-:
With this Werk, a debugging message will be shown instead.
ID: 13985
Title: 'debug' setting will no longer try to load a non existing JavaScript file
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Enabling 'debug' in the front end setting would try to load a non minified JavaScript file.
As Source Maps are used for debugging, this file is not present on the Checkmk server.
The setting will no longer cause the UI to try to load the non existing file.
ID: 15488
Title: Allow configuration of backups for remote sites
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0b7
If you tried to configure a backup for a remote site of a customer with
disabled option "Disable remote configuration" for that site, the message
"Check_MK can only be configured on the managers central site." was shown. This
made it impossible to configure a backup for such remote sites.
ID: 15609
Title: KUBE: Limit collection time for <tt>Persistent Volume Claims & Persistent Volumes</tt>
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0b7
This change affects those using the <tt>Kubernetes</tt> together with the feature <tt>Collect
information about Persistent Volume Claims & Persistent Volumes</tt> (available in 2.2.0 and above).
With this feature turned on, the Kubernetes agent will contact the kubelet on each node via a proxy
provided by the Kubernetes API server. This means the data collection depends on the number of
nodes and the latency of the Pod network. If this data collection takes too long, the Kubernetes
agent may timeout. This in turn causes the previously collected API data to be discarded.
With this Werk, the data collection time is limited to 30 seconds. The omission of the data causes
the omission of metrics from the <tt>PVC</tt> service of a Pod. This is consistent with how missing
data is handled, if the corresponding kubelet is down.