Julian Pelizäus
Julian Pelizäus
Hi, from the [docs](https://canonical-microceph.readthedocs-hosted.com/en/squid-stable/how-to/configure-rbd-mirroring/) it was not clear how to enable replication using type snapshot so I ended up trying to enable it on pool level which (according to upstream...
The status endpoint should return the currently used cluster certificate. This can be helpful for to identify which certificate is currently used when talking e.g. talking to cluster manager
Recently we ran into trouble with the dependency to the `lxd/response` package downstreams have to use when defining their microcluster API handlers. If they the version used for defining the...
Preceded by: * https://github.com/canonical/lxd/pull/15775 * https://github.com/canonical/lxd/pull/15776 * https://github.com/canonical/lxd/pull/15777 ### Overview This PR uses the new backup config metadata format introduced in https://github.com/canonical/lxd/pull/15129 to track all of an instance's custom storage...
### Issue description This potentially affects all versions of LXD. I have encountered this error once during the execution of the `standalone/ceph` test suite https://github.com/canonical/lxd/actions/runs/15585238643/job/43890255752?pr=15523#step:15:64850. When mapping a volume to...
### Output of "snap list --all lxd core20 core22 core24 snapd" ```shell Affects both `5.21/edge` and `latest/edge`. ``` ### Issue description In the MicroCloud test suite we sometimes see the...
### Issue description When restoring a cluster member using `lxc cluster restore`, the daemon won't wait until both the networks and storage pools are ready. Storage pools are always started...
During the introduction of the storage connectors package (https://github.com/canonical/lxd/pull/14710) we found that we have to wait for volume resizes to take effect on the actual block device mapped to the...
Affected version: `squid/stable` A three member MicroCeph cluster (each node with one OSD) cannot be scaled down to two members because MicroCeph fails with the following error: ```bash root@micro01:~# microceph...
I'll create this issue based on our recent discussion in Frankfurt. When running the `microceph replication enable` command, a user has to provide the name of the storage pool (resource)...