-
### Bug Description
ConnectionError on configure event
### To Reproduce
juju deploy
### Environment
microk8s
### Relevant log output
```shell
unit-eupf-k8s-0: 15:23:34 ERROR unit.eupf-k8s/0.juj…
-
Currently, the charm includes the following in `metadata.yaml`:
```
assumes:
- k8s-api
```
However, the current version of the charm requires Juju 3.4.3 or greater because of the fixes to t…
-
## Steps to reproduce
1. Deploy `kafka-k8s` (3/stable, revno. 56) and `zookeeper-k8s`
2. Deploy a Kafka interface consumer
3. Relate everything together
4. Break the relation between `kafka-…
-
The following select statement will return no error, even though the table in question does not have a charm by the name of `juju-controller`.
Table contents:
```
uuid …
-
## Steps to reproduce
- start a cluster with three nodes
- remove the application
- after the first unit is removed, occasionally (e.g. when the application leader gets removed first) some shards a…
-
When COU refresh vault from 1.7/stable to 1.8/stable during Jammy/Yoga -> Jammy/Zed upgrade, the vault charm goes into error state with `Connection Refused` error:
```
unit-vault-0: 03:48:42 WARNI…
-
## Steps to reproduce
Shut down and resart the server hosting the Juju model.
Opensearch units will be blocked on `net.ipv4.tcp_retries2 should be 5 `
Destroy a unit and add a new one.
The new one…
-
### Bug Description
I am not able to upgrade an already related grafana-agent on arm substrate from rev 108 to 166 . It goes into error state with a failed upgrade-charm hook:
```
foo@bar:~$ ju…
-
### Context
Based on the discussion in https://github.com/canonical/bundle-kubeflow/issues/940, we want to make sure the public documentation for Charmed Kubeflow shows the right version of juju to u…
-
### Bug Description
After integrating grafana-agent in Charmed Kubernetes with Loki, loki breaks with `hook failed: "logging-relation-departed"`
### To Reproduce
1. deploy charmed kubernetes with g…