Re: [ceph-users] Bright new cluster get all pgs stuck in inactive

2019-01-29 Thread Paul Emmerich
ot;item": -1, > > "item_name": "default" > > }, > > { > > "op": "chooseleaf_firstn", > > "num": 0, > > "type": "chassis" > > }, > > { > > "op": "emit" &g

Re: [ceph-users] Bright new cluster get all pgs stuck in inactive

2019-01-29 Thread PHARABOT Vincent
"op": "take", "item": -1, "item_name": "default" }, { "op": "chooseleaf_firstn", "num": 0, "type": "host"

Re: [ceph-users] Bright new cluster get all pgs stuck in inactive

2019-01-29 Thread PHARABOT Vincent
"num": 0, "type": "host" }, { "op": "emit" } ] } ] De : Jean-Charles Lopez [mailto:jelo...@redhat.com] Envoyé : mardi 29 janvier 2019 19:30 À : PHARABOT Vincent Cc :

Re: [ceph-users] Bright new cluster get all pgs stuck in inactive

2019-01-29 Thread Jean-Charles Lopez
Hi, I suspect your generated CRUSH rule is incorret because of osd_crush_cooseleaf_type=2 and by default chassis bucket are not created. Changing the type of bucket to host (osd_crush_cooseleaf_type=1 which is the default when using old ceph-deploy or ceph-ansible) for your deployment should f