rook: rabbitmq not binding to block storage
Bug Report
What happened: rabbitmq failed with: PersistentVolumeClaim is not bound: “rabbitmq-rabbitmq” (repeated 5 times)
What you expected to happen: rabbit to start sucessfully
How to reproduce it (minimal and precise):
Create AKS cluster 1.8.2 on Azure, 5 node, 300GB SSD OS Drive
helm install --name rook --namespace rook-system rook-master/rook --set rbacEnable=false
kubectl create -f rook-cluster.yaml
kubectl create -f rook-storageclass.yaml
helm install --name rabbitmq --set persistence.storageClass=rook-block stable/rabbitmq
Logs
root@rook-tools:/# ceph status
cluster:
id: c3628414-b9f4-46f8-8bd8-9648d45e0435
health: HEALTH_OK
services:
mon: 3 daemons, quorum rook-ceph-mon1,rook-ceph-mon2,rook-ceph-mon0
mgr: rook-ceph-mgr0(active), standbys: rook-ceph-mgr1
osd: 5 osds: 5 up, 5 in
data:
pools: 1 pools, 100 pgs
objects: 1 objects, 8 bytes
usage: 105 GB used, 1448 GB / 1553 GB avail
pgs: 100 active+clean
root@rook-tools:/# rookctl status
OVERALL STATUS: OK
USAGE:
TOTAL USED DATA AVAILABLE
1.52 TiB 105.03 GiB 8 B 1.41 TiB
MONITORS:
NAME ADDRESS IN QUORUM STATUS
rook-ceph-mon1 10.0.85.215:6790/0 true OK
rook-ceph-mon2 10.0.131.231:6790/0 true OK
rook-ceph-mon0 10.0.253.167:6790/0 true OK
MGRs:
NAME STATUS
rook-ceph-mgr0 Active
rook-ceph-mgr1 Standby
OSDs:
TOTAL UP IN FULL NEAR FULL
5 5 5 false false
PLACEMENT GROUPS (100 total):
STATE COUNT
active+clean 100
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 21 (9 by maintainers)
@AceHack , @galexrt : It looks like this is supported but you need to enable it. See: http://ceph.com/community/new-luminous-erasure-coding-rbd-cephfs/
You need to run a command like
ceph osd pool set POOL_NAME allow_ec_overwrites trueI wonder how Rook should enable this through the CRD’s or if it should always be enabled.