Closed gustavosr98 closed 2 weeks ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-5716.
This message was autogenerated
It actually looks like after sometime the blocked status gets solved
# ubuntu@microk8s:~$ juju status
Model Controller Cloud/Region Version SLA Timestamp
pg micro-localhost micro/localhost 3.5.4 unsupported 19:43:48Z
App Version Status Scale Charm Channel Rev Address Exposed Message
data-integrator active 1 data-integrator latest/edge 72 10.152.183.60 no
grafana-agent-k8s 0.40.4 blocked 1 grafana-agent-k8s latest/edge 95 10.152.183.241 no Missing ['grafana-cloud-config']|['grafana-dashboards-provider'] for grafana-dashboards-consumer; ['grafana-cloud-con...
pgbouncer-k8s 1.21.0 active 1 pgbouncer-k8s 1/edge 329 10.152.183.98 no
postgresql-k8s 14.13 active 2 postgresql-k8s 14/edge 431 10.152.183.72 no
postgresql-test-app active 1 postgresql-test-app latest/edge 273 10.152.183.182 no received database credentials of the first database
s3-integrator blocked 1 s3-integrator latest/edge 73 10.152.183.164 no Missing parameters: ['access-key', 'secret-key']
self-signed-certificates active 1 self-signed-certificates latest/edge 202 10.152.183.38 no
sysbench waiting 1 sysbench latest/edge 91 10.152.183.200 no installing agent
Unit Workload Agent Address Ports Message
data-integrator/0* active idle 10.1.128.200
grafana-agent-k8s/0* blocked idle 10.1.128.203 Missing ['grafana-cloud-config']|['grafana-dashboards-provider'] for grafana-dashboards-consumer; ['grafana-cloud-con...
pgbouncer-k8s/0* active idle 10.1.128.202
postgresql-k8s/0 active idle 10.1.128.208
postgresql-k8s/1* active idle 10.1.128.209 Primary
postgresql-test-app/0* active idle 10.1.128.204 received database credentials of the first database
s3-integrator/0* blocked idle 10.1.128.207 Missing parameters: ['access-key', 'secret-key']
self-signed-certificates/0* active idle 10.1.128.210
sysbench/0* waiting idle 10.1.128.211 Waiting on data from relation
Hi, to provide some context, before the data-integrator to Pgbouncer relation can be established, the backend Pgbouncer to Postgresql relation must be ready.
Steps to reproduce
Just deploy the bundle
Expected behavior
data-integrator not to be in blocked state
Actual behavior
Versions
Juju: 3.5/stable Bundle version: 14/edge rev161 microk8s: 1.30/stable
Log output
Additional context
grafana-agent is expected. I did not added a relation to COS.
s3-integrator is expected. I did not provide S3 credentials.
data-integrator is missing database-name config so manually added it.
juju config data-integrator database-name=testdb