ID: 14396
Title: Netapp filer connection bug when using more than 500 instances
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
When querying a netapp instance with more than 500 instances the "NetApp filer connection" service would show that we exeeded the max-records limit.
This has been fixed now. No user interaction required.
ID: 13933
Title: missing Theme in REST API
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
Some Rulesets regarding themes and icons could crash in the REST API due
to a missing reference to a default Theme. The theme was previously omitted
in the REST API which led to this error.
This has now been fixed and a default theme is now available in the REST API
for Ruleset validation logic to access, even though it has no effect for the user.
ID: 13934
Title: REST API: add effective_attribute switch to host list
Component: REST API
Level: 1
Class: New feature
Version: 2.2.0i1
This werk adds the "effective_attributes" switch to the host
configuration list endpoint of the REST API. If it is switched
to "true" all "effective attributes" will also be returned for
each host in the returned list. The default is "false" because
of performance reasons.
ID: 14100
Title: df: ignore "<i>Filesystem grouping patterns</i>" ruleset
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
The following change only affects the discovery of the <tt>df</tt> check plugin.
All other "<i>Filesystem</i>" services are not affected.
The service discovery of the <tt>df</tt> plugin no longer respects rules configured using the "<i>Filesystem grouping patterns</i"< ruleset.
The discovery of the <tt>df</tt> plugin can also be configured by the ruleset "<i>Filesystem discovery</i>", which now supports the configuration of those grouping patterns.
If you configured such grouping patterns for the <tt>df</tt> check, you have to add the corresponding options to the ruleset "<i>Filesystem discovery</i>".
<b>Note:</b> For the "<i>Filesystem grouping patterns</i>" ruleset all matching rules were applied, whereas rules of the ruleset "<i>Filesystem discovery</i>" are merged.
This means that now only the grouping patterns of the first matching rule are applied for each host.
We appreciate this incompatibility is an inconvenience, but is is necessary to be able to move forward.
ID: 13681
Title: Agent Bakery: Target platform selection
Component: agents
Level: 1
Class: New feature
Version: 2.2.0i1
It's now possible to narrow down the target platforms (i.e., the operating system and
package format) for baked agent packages.
This can be configured by choosing the desired platforms at the "Select packages" entry of the
"Agent Bakery Packages" ruleset. Unselected packages will show the text "Not available" instead
of a download button in the baked packages overview. If no "Select packages" rule entry is
activated, the agent bakery defaults to bake for all platforms.
As the selection is done via a ruleset, it only influences the matching agent configurations,
rather than narrowing down the target platforms globally.
As a result, if you unselect all target platforms, the resulting agent configurations/packages
will vanish completely from the agent bakery.
Also, you can't narrow down the VANILLA packages with this rule. (However, they have a minimal
impact on the overall baking time, so there's no need to deactivate unneeded packages)
Note: To keep things together, the new "Agent Bakery Packages" ruleset is also used to
activate/deactivate agent package compression, which has been configured at the "Agent bakery
package compression" ruleset before. Your existing configurations are ported automatically.
ID: 14399
Title: PATH update of linux agent when deployed via bakery
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
When deploying the linux agent via bakery and setting a custom installation path the async agent would randomly crash after about a week.
This has been due to a wrong update of the PATH variable. This has been fixed now.
To fix crashing agents, create a new agent package and update affected machines.
ID: 14400
Title: parsing zpool status when pool contains special vdev
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
In version 0.8.x a special top level vdev was introduced [1]. A zpool status check would crash
with an IndexError. This has beeen fixed now. No user interaction requried.
[1]: https://github.com/openzfs/zfs/pull/5182
ID: 14317
Title: filesystem: use default thresholds for inodes when no levels are configured
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The incompatibility of this werk affects users who have services of inode
capable filesystems.
Due to a bug, default thresholds for inodes were never used by the
<tt>filesystem</tt> checks. This has been fixed: by default, the check shows a
WARN state when 10% of inodes are free or fewer, and a CRIT state when 5% of
inodes are free or fewer.
If you do not wish to apply any levels, it is possible to deactivate thresholds
by setting the "Levels for inodes" configuration option to "Ignore levels" in
the corresponding ruleset.
ID: 14318
Title: df: always show thresholds in configured units when applying magic factor
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
When magic factor was used in combination with absolute filesystem levels (in
MB), the check summary of the <tt>df</tt> check would show percentage
thresholds. The check now shows thresholds in the same unit as it was
configured with.
ID: 14478
Title: Restrict path param in cookies
Component: Setup
Level: 1
Class: Security fix
Version: 2.2.0i1
The Path parameter of the cookies used to be set to '/'. Now it is restricted to the site URL prefix '/[SITE_ID]'.