Comment 2 for bug 1849897

As a workaround, the check can be removed by injecting updated relation data.

Example:

$ juju run -u nova-cloud-controller/0 -- relation-ids nrpe-external-master
nrpe-external-master:257

$ juju run -u nova-cloud-controller/0 -- relation-list -r257
nrpe-container/38

$ juju run -u nrpe-container/38 -- relation-get -r257 - nova-cloud-controller/0

[...checks are here...]

Save the monitors in a file, remove the nova-api-os-compute check:

$ cat monitors.lp1849897.out
monitors:
  remote:
    nrpe:
      apache2: {command: check_apache2}
      haproxy: {command: check_haproxy}
      haproxy_queue: {command: check_haproxy_queue}
      haproxy_servers: {command: check_haproxy_servers}
      memcached: {command: check_memcached}
      nova-conductor: {command: check_nova-conductor}
      nova-consoleauth: {command: check_nova-consoleauth}
      nova-novncproxy: {command: check_nova-novncproxy}
      nova-scheduler: {command: check_nova-scheduler}

Now set the amended relation data:

$ juju run -u nova-cloud-controller/0 -- relation-set -r257 monitors="$(cat monitors.lp184
9897.out)"