ntpmon embedded in the published version is not the same as the current layer

[Junien F]

Hi,

I just installed the "telegraf" and "ntp" charms on a unit. Each of them provided ntpmon, telegraf in /opt/ntpmon, and ntp in /opt/ntpmon-ntp-charm.

However, the telegraf version appears to be stale and doesn't recognize chrony, so it tries to run ntpq, which fails.

While looking into this, I actually never found where the "ntpmon.py handling chrony" source code comes from. "charm build" of the ntp charm does not result in what's currently in the charmstore. It's probably because the "bionic-chrony" branch of https://code.launchpad.net/ntpmon needs to be merged into master.

Also, why are both telegraf and the ntp charm providing this code ? What's the correct way to configure both of them when they're installed together ?

Thanks

[Paul Gear (paulgear)]

https://github.com/paulgear/ntpmon/pull/3 is where this merge is being handled. I've pushed an update and added some comments there, built a new charm and pushed to cs:~paulgear/telegraf, and started a CI run.

[Paul Gear (paulgear)]

The upstream NTPmon changes have been merged into master. I've built a new version of the telegraf charm and pushed it to cs:~te​legraf-charmers/tele​graf-35 (candidate channel). But CI seems to be a bit borked at the moment, so I'm not ready to declare this fixed. When it gets a successful CI run, I think we're good to go.