ID: 14392
Title: Consistently handle white-space in passwords
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously it was not possible to set user passwords starting with or ending on white-space characters in the Edit Users UI. This is now possible.
White-space characters at be beginning or end of passwords were stripped in the Edit Users interface. For example, the password "insecure example " would have been accepted by the interface, but modified to "insecure example". As a result, users might have ended up with a different password than they expected and been unable to log in.
White-spaces in passwords are now no longer stripped, so the password "insecure example " can be set and used.
Note that the user's Change Password interface, reachable via the User Profile section, was not affected by this and has already allowed passwords starting with or ending on white-space characters.
ID: 14997
Title: Fix wrong negate value for "Host Auxiliary Tags" filter
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
If a view used the filter "Host Auxiliary Tags", the selected tags always
showed the negate option as active on edit of the view.
On save this negate option would be saved, leading to unintended results in the
view.
ID: 14993
Title: reports: Fix possible KeyError on update from 2.0 to 2.1
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 2.2.0i1
If you had reports configured in 2.0 with datasource "customer" and a customer
defined in "Context / Search Filters", the update to 2.1 showed the error
"KeyError: 'customer'".
Since the UI was unusable after that error, a possible workaroud was to search
for affected reports in ~/var/check_mk/web, e.g. with:
find . -name 'user_reports*' -exec grep -l "'context': {'customer'" {} \;
If you changed "'context': {'customer':'mycustomer'}" in the found files to
"'context': {}" and deleted the cache file
~/tmp/check_mk/visuals_cache/cached_reports, the UI was usable again und you
could configure the customer in the report again.
ID: 14788
Title: Regression in mk_docker.py: unexpected keyword argument 'ignore_removed'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
If you're using mk_docker.py and the python docker library in version < v3.3.0, you're affected by this since werk #14864.
The traceback may look like:
<tt>
list() got an unexpected keyword argument 'ignore_removed'
</tt>
This is fixed now.
ID: 14984
Title: MKP manager commandline interface: Fix 'remove' and 'disable' commands
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The <tt>mkp remove</tt> command (or <tt>cmk -P remove</tt>) has been fixed to reflect the recent changes in the GUI.
You can only remove <i>disabled</i> packages.
The 'disable' command to do this was intruced with 2.0.0p30, but defunct.
It is now fixed.
Since you can have different versions of the same package uploaded, you have to specify the version as well now:
<tt>mkp remove NAME VERSION</tt>
ID: 12524
Title: CME: Allow two custom logo uploads
Component: Multisite
Level: 1
Class: New feature
Version: 2.2.0i1
Instead of only one logo for both the login mask and the navigation bar, admins of a CME installation can now upload two separate logos, with different size restrictions for the two differnt UI places.
The login logo is restricted to 120px width and 36px height, the navigation bar logo is restricted to 48px width and 48px height.
When updating from an earlier version without this change, any custom logos are removed.
ID: 14787
Title: Extend service detection for MariaDBs with mk_mysql.vbs
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
You're affected by this werk if you're monitoring MariaDBs with mk_mysql.vbs and you've given a customized service name.
Perviously, the Windows Service was only detected, if it contained the "MariaDB" suffix.
Now Windows Services containing the substring "MariaDB" will be detected (e.g. "MariaDB 10.4.25").
ID: 15031
Title: host_config & dcd: change SiteField field to use configured_sites rather than enabled_sites
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
Prior to this werk, the REST API endpoint show all hosts returned a 500 error when one of the returned
hosts was part of a disabled remote site. This error also affected the DCD as the connector uses the
same endpoint to retrieve the hosts. This werk resolves this error by changing the site verification
from using all configured sites rather than all enabled sites.
ID: 14894
Title: Fix availability timeline based on service times
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
If the computation option "Base report only on service times" was used, the
timeline did not display the entries correctly. In some cases the service
period was still shown until the end of the timeline, even if this period had
already ended.
ID: 14700
Title: azure_status: Monitor Azure Status
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
It's now possible to monitor Azure Status from
https://azure.status.microsoft/en-us/status in Checkmk.
One new check has been added, Microsoft Azure: Status.
To monitor Azure Status you have to configure the related
special agent Microsoft Azure Status.