Hi Checkmk Community,
We have a new .mkp file, which works fine in our Checkmk installations. I tried to upload it to the Checkmk Exchange but get an error message, as shown below.
Hi Robert,
thanks, I checked that. The versioning scheme matches the requirement of semantic versioning
Here is the screen from Checkmk. Nothing fancy IMHO
Hi Andreas,
this is the directory of the .mkp shown via tar -tzvf
-rw-r–r-- 0/0 3342 2025-01-16 15:58 info
-rw-r–r-- 0/0 2080 2025-01-16 15:58 info.json
-rw-r–r-- 0/0 51200 2025-01-16 15:58 cmk_addons_plugins.tar
-rw-r–r-- 0/0 10240 2025-01-16 15:58 cmk_plugins.tar
-rw-r–r-- 0/0 10240 2025-01-16 15:58 web.tar
Do you need to see the content of the 3 tar files as well?
it extends the genua.py file as an overlay to detect additional genua appliance models. In Checkmk, the mkp behaves as as expected (at least on first sight). Maybe the Exchange validation is too restrictive?
Yes that can be - it was the same problem with my Redfish mkp for 2.3. It was working fine but could not be uploaded to the exchange as all the files where inside “cmk\plugins”.
It is a known problem. Good news is that there will be changes on the Exchange soon, and the validation issues should also be resolved then
Cannot give you any timeframes at the moment, but it should happen in the near future, from what I know
Same issue here, I can not update the Cisco Meraki special agent on the Exchange. I guess it’s also an issue with the “cmk_plugins.tar” in the MKP