Comment 5 for bug 1929262

> > client.prometheus-ceph-exporter at v1:10.0.0.123:0/2623829913 is using insecure global_id reclaim
>
> Can we rebuild the prometheus-ceph-exporter snap to pull up-to-date librados properly as a short-term solution here?

The following patch would be band-aid, and I've confirmed it's working with focal-ussuri(Octopus).

https://github.com/nobuto-m/snap-prometheus-ceph-exporter/compare/stable/3.0.0-nautilus...3.0.0-nautilus/edge
$ git diff stable/3.0.0-nautilus
diff --git a/snapcraft.yaml b/snapcraft.yaml
index 5316954..0dc2ca4 100644
--- a/snapcraft.yaml
+++ b/snapcraft.yaml
@@ -5,9 +5,16 @@ summary: Prometheus Ceph Exporter
 description: |
   Exporter that exposes information gathered from Ceph for use by the Prometheus monitoring system
 confinement: strict
+package-repositories:
+ - type: apt
+ components: [main]
+ suites: [bionic-updates/ussuri]
+ key-id: 391A9AA2147192839E9DB0315EDB1B62EC4926EA
+ url: http://ubuntu-cloud.archive.canonical.com/ubuntu
 parts:
   ceph-exporter:
     plugin: go
+ go-channel: 1.13/stable
     source: https://github.com/digitalocean/ceph_exporter.git
     go-importpath: github.com/digitalocean/ceph_exporter
     source-tag: 3.0.0-nautilus

Just for the record, using "nautilus" branch in the upstream(digitalocean) exporter doesn't work out of the box. It requires another hack to make it work with the existing scheme with our charm. Also, it's not compatible from an exporter output point of view so it actually breaks some graphs set up by the charm...
https://github.com/nobuto-m/snap-prometheus-ceph-exporter/compare/stable/3.0.0-nautilus...nautilus/edge

Upgrading to core20 instead of cloud-archive:ussuri didn't work either.
https://snapcraft.io/docs/go-plugin#heading--core20
"The go plugin in core20 exclusively required the use of go.mod"
So the build fails without cherry-picking go.mod changes in the upstream on top of the 3.0.0-nautilus tag.