Hi @marian, from the logs this looks like your env is a microk8s charm based deployment that has ceph-csi charm units in the model. Ceph/mk8s integration wouldn't use the ceph-csi charm, so perhaps the env is dirty from previous validation runs?
That was fixed in charmed k8s 1.29+ck1 (released late april 2024). I'm gonna mark this bug as invalid for now and ask that you confirm with charmed-k8s + ceph-csi at 1.29+ck1 (or greater) to weed out any env and/or duplicate fixes. Thank you!
Hi @marian, from the logs this looks like your env is a microk8s charm based deployment that has ceph-csi charm units in the model. Ceph/mk8s integration wouldn't use the ceph-csi charm, so perhaps the env is dirty from previous validation runs?
If not, it looks similar to: https:/ /bugs.launchpad .net/charm- ceph-csi/ +bug/2035393
Which we determined to be invalid because the actual root cause was an invalid namespace prior to having the ceph manifests deployed: https:/ /bugs.launchpad .net/charm- ceph-csi/ +bug/2053265
That was fixed in charmed k8s 1.29+ck1 (released late april 2024). I'm gonna mark this bug as invalid for now and ask that you confirm with charmed-k8s + ceph-csi at 1.29+ck1 (or greater) to weed out any env and/or duplicate fixes. Thank you!