You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a feeling there is an obvious answer to this, but I recently upgraded my CheckMK server from 2.3.0p17 to 2.3.0p18 (at home not the much larger install at work). I then upgraded the YUM MKP from 2.4.4 to 2.5.1 and re-baked packages for the single agent that I deploy the yum plugin onto using an agent rule. It is a Cloud edition server and I noticed that the AGENT upgraded, but the YUM plugin that was previously deployed into /usr/lib/check_mk_agent/plugins/300 was removed. No other options were changed, just an update to the plugin and the version number.
Has something changed in 2.5.1 from 2.4.4 that would prevent the plugin being packaged correctly into the RPM for install - I did open the RPM and there was no YUM plugin file in the archive.
The text was updated successfully, but these errors were encountered:
@swampdogmash sorry for the late reply.
I installed plugin version 2.5.1 on a little outdated 2.3.0p9 Checkmk instance and found the plugin baked into the agent RPM file. Maybe latest Checkmk server version causes this problem?
I have a feeling there is an obvious answer to this, but I recently upgraded my CheckMK server from 2.3.0p17 to 2.3.0p18 (at home not the much larger install at work). I then upgraded the YUM MKP from 2.4.4 to 2.5.1 and re-baked packages for the single agent that I deploy the yum plugin onto using an agent rule. It is a Cloud edition server and I noticed that the AGENT upgraded, but the YUM plugin that was previously deployed into /usr/lib/check_mk_agent/plugins/300 was removed. No other options were changed, just an update to the plugin and the version number.
Has something changed in 2.5.1 from 2.4.4 that would prevent the plugin being packaged correctly into the RPM for install - I did open the RPM and there was no YUM plugin file in the archive.
The text was updated successfully, but these errors were encountered: