Missing one of (Loki|filebeat), one of (Prometheus|target|nrpe) relation(s)

VariableDeclared commented 8 months ago

Bug Description

Hello -

When relating COS proxy with various relations the charm will get stuck in "Missing one of (Loki|filebeat), one of (Prometheus|target|nrpe) relation(s)", despite the relations existing.

To Reproduce

Deploy Openstack/PCB

Relate cos proxy wiith the following relations

- - ceph-dashboard:grafana-dashboard
- cos-proxy:dashboards
- - ceph-mon:prometheus
- cos-proxy:prometheus-target
- - cos-proxy:dashboards
- etcd:grafana
- - cos-proxy:dashboards
- prometheus-grok-exporter:dashboards
- - cos-proxy:dashboards
- prometheus-openstack-exporter:dashboards
- - cos-proxy:dashboards
- telegraf:dashboards
- - cos-proxy:filebeat
- filebeat:logstash
- - cos-proxy:juju-info
- filebeat:beats-host
- - cos-proxy:juju-info
- landscape-client:container
- - cos-proxy:juju-info
- nrpe:general-info
- - cos-proxy:juju-info
- prometheus-grok-exporter:juju-info
- - cos-proxy:juju-info
- telegraf:juju-info
- - cos-proxy:juju-info
- ubuntu-advantage:juju-info
- - cos-proxy:monitors
- nrpe:monitors
- - cos-proxy:prometheus-rules
- telegraf:prometheus-rules
- - cos-proxy:prometheus-target
- telegraf:prometheus-client
- loki:logging
- - cos-proxy:downstream-prometheus-scrape
- prometheus:metrics-endpoint
- - cos-proxy:downstream-grafana-dashboard
- grafana:grafana-dashboard
- - cos-proxy:downstream-prometheus-scrape
- scrape-interval-config:configurable-scrape-jobs
- - cos-proxy-monitors:downstream-prometheus-scrape
- scrape-interval-config:configurable-scrape-jobs
- - cos-proxy-monitors:monitors
- nrpe:monitors
- - prometheus-libvirt-exporter:dashboards
- cos-proxy:dashboards
- - prometheus-libvirt-exporter:scrape
- cos-proxy:prometheus-target
- - prometheus-openstack-exporter:prometheus-openstack-exporter-service
- cos-proxy:prometheus-target

Observe cos-proxy in blocked state

[Workaround]

To follow

Thank you, Peter

Environment

Openstack PCB Microk8s on OAM network with Metal-LB

Relevant log output

to follow

Additional context

No response

natalytvinova commented 8 months ago

Seeing the same issue, it might be related to an order in which the relations are applied, we're looking into that

simskij commented 6 months ago

What revision did you see this in?

slapcat commented 4 months ago

We are seeing this issue too on a newly deployed cos-proxy:

Model  Controller        Cloud/Region  Version  SLA          Timestamp
ceph   foundations-maas  maas_cloud    2.9.44   unsupported  22:31:13Z

SAAS          Status  Store            URL
grafana       active  mk8s-controller  admin/cos.grafana
loki          active  mk8s-controller  admin/cos.loki
prom-metrics  active  mk8s-controller  admin/cos.prom-metrics
prometheus    active  mk8s-controller  admin/cos.prometheus

App                           Version  Status       Scale  Charm                               Channel        Rev  Exposed  Message
cos-proxy                     n/a      blocked          1  cos-proxy                           latest/stable   82  no       Missing one of (Grafana|dashboard|grafana-agent), one of (Loki|filebeat), one of (Prometheus|target|nrpe|grafana-agen...

Relation provider                                  Requirer                             Interface               Type         Message
loki:logging                                       cos-proxy:downstream-logging         loki_push_api           regular  
cos-proxy:downstream-grafana-dashboard             grafana:grafana-dashboard            grafana_dashboard       regular      
cos-proxy:downstream-prometheus-scrape             prometheus:metrics-endpoint          prometheus_scrape       regular

The deployment steps:

juju deploy cos-proxy --channel=latest/stable
juju relate cos-proxy prometheus
juju relate cos-proxy loki
juju relate cos-proxy grafana

Happy to provide any additional info you may need.

canonical / cos-proxy-operator