ID: 6511
Title: Global Settings: Custom localizations fixed possible exception when language alias contains non-ascii characters
Component: WATO
Level: 1
Class: Bug fix
Version: 1.6.0i1
An exception could occur when using a localized GUI and a language which uses non-ascii characters
in it's alias file (local/share/check_mk/locale/[lang]/alias).
ID: 6471
Title: New Theme: Updated fixes
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
This werk includes some minor fixes for:
- Missing highlighting of ineffective rules
- Too small arrow WATO > Hosts for folder order
- White title of folder if the folder is locked
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: 6457
Title: IPMI Management board: Improved error handling when sensors can not be read
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.6.0i1
When the IPMI sensors can not be read because of an incompatible device, the
error is now handled more gracefully. The other IPMI data, like firmware information,
is fetched even when the sensors can not be read and the exceptions are visible on
the command line when executing e.g. cmk -vd [hostname] or cmk -vvd [hostname].
ID: 6458
Title: IPMI Management board: Use USER privilege level for monitoring
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.6.0i1
Previous versions used the ADMIN privilege level for monitoring via IPMI which
is way too much for this read-only access which is needed by Check_MK for
monitoring.
When you tried to use a non ADMIN privileged user before, an error like this occured:
ERROR: Requested privilege level is not allowed over this channel while
requesting privelege level 3 for [user]
You can now use less privileged users for monitoring.
ID: 6455
Title: LDAP: Multiple sync processes could be running at the same time
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
Since 1.5.0b2 (#5986) the user synchronization is executed as background
job. Because of a broken locking the sync could be executed multiple times
in parallel. This issue did not lead to corrupted data, there were multiple
jobs running in parallel overwriting each others results.