-
### Description
Rook (Ceph) fails starting correctly after upgrading to runc v1.2.0. Rolling back to runc v1.1.15 fixes all errors.
### Steps to reproduce the issue
1. Install rook operator v1.15.3…
-
Bug Report
**Maybe i have done something wrong it would be really helpful if someone can help me with that**⚠️
Deviation from expected behavior:
Everything seems to work correctly, except that the …
-
When connecting rook to an external ceph object store (with existing external RGW), only for the sake of bucket management, it seems that I still need to create an (external) CephCluster resource toge…
-
**Is this a bug report or feature request?**
* Bug Report
**Deviation from expected behavior:**
With 8 ceph clusters managed by rook, the operator is heavily throttled by Kubernetes. There ar…
dimm0 updated
1 month ago
-
Following tier1 testcase is failing on IBM Power:
```
tests/functional/monitoring/prometheus/alerts/test_alerting_works.py::test_prometheus_rule_failures
```
error being:
```
There …
-
# Describe the bug #
I see a way to enable read affinity and pass crush location labels in CephConnection CR which I did
```
$ k get cephconnections.csi.ceph.io ceph-cluster -ojsonpath='{.spec}' …
-
localhost:/home/jhs/rook/deploy/examples # kubectl get pods -n rook-ceph
NAME READY STATUS RESTARTS AGE
csi-cephfsplugin-lfdmh …
-
**Is this a bug report or feature request?**
* Bug Report
**Deviation from expected behavior:**
Annotations defined in cluster CR may be applied to wrong daemon (in addition to the correct …
-
Hi Team,
i have installed the rook-ceph cluster on k8s environment , from tools pod not able to get the ceph status what might be the reason, i can see cephfs is failed status but still its should …
-
**Is this a bug report or feature request?**
* Bug Report
**Deviation from expected behavior:**
When using the `rook-ceph` helm chart version `1.15.6`, `.dicover.resources` does not work well…