I am currently in the process of updating an old 2.2.0p27 EE instance to 2.3.0p30 EE, which is quite a journey because there are a lot of custom written checks, which are not packed into mkps or documented. Most of them are already running in legacy mode in 2.2…
But that is not my main problem. While updating the instance to 2.3 I already get the following warning:
Ignoring outdated plugin ‘rds_licenses’: Format no longer supported – this API is deprecated!
After successfully updating, starting the instance and applying the pending changes I get the following warning:
check_mk: Found configured rules of deprecated check group “rds_licenses”. These rules are not used by any check plug-in. Maybe this check group has been renamed during an update, in this case you will have to migrate your configuration to the new ruleset manually. Please check out the release notes of the involved versions. You may use the page “Deprecated rules” in the “Rule search” to view your rules and move them to the new rulesets. If this is not the case, the rules could be related to a disabled or removed extension package (mkp). You would have to enable/upload the corresponding package and remove the related rules before disabling/removing the package again.
In the Release notes for 2.3.0b1 ([Release] Checkmk beta release 2.3.0b1) I could find the Werk 15474 (Werk #15474: rds_licenses: Windows Server 2022 enabled in RDS Licenses check) which indicates that this check was not deprecated and is still supported.
In “Setup => General => Rule search: Deprecated rulesets” the rds_licenses is nowhere to be seen.
Does anyone have a idea why cmk thinks its buildin check is deprecated and no longer working or give me a hint how to debug this problem?