Yeah. It was the _no_schedule label. After removing it the host got the keyring and ceph.conf files. Should I open a bug somewhere? On Tue, 2022-08-02 at 08:39 -0400, Adam King wrote: > It's possible there's a bug in cephadm around placements where hosts have the _no_schedule label. > There was https://tracker.ceph.com/issues/56972 recently for an issue with how _no_schedule > interacts with placements using explicit hostnames. It might be something similar here where it > thinks there's no hosts matching the placement because all the matching hosts have the > _no_schedule label. I'd maybe try removing _no_schedule from one of the hosts and see if the > warning goes away. > > On Tue, Aug 2, 2022 at 7:53 AM Carlos Mogas da Silva <r3pek@xxxxxxxxx> wrote: > > Hi! > > > > I've followed [1] to add a keyring under management that would be deployed to my k8s cluster. > > I've also added the k8s cluster hosts with the "_no_schedule" and "k8s" label. > > ceph orch seems to know that everything is fine: > > # ceph orch host ls --label k8s > > HOST ADDR LABELS STATUS > > k8s-master 10.1.0.4 _no_schedule k8s > > k8s-worker1 10.1.0.5 _no_schedule k8s > > k8s-worker2 10.1.0.6 _no_schedule k8s > > 3 hosts in cluster who had label k8s > > > > But on the ceph logs I'm getting this warnings: > > [WRN] unable to calc client keyring client.k8s placement PlacementSpec(label='k8s'): Cannot > > place : > > No matching hosts for label k8s > > > > Did I miss something? > > > > [1] https://docs.ceph.com/en/quincy/cephadm/operations/#client-keyrings-and-configs > > _______________________________________________ > > ceph-users mailing list -- ceph-users@xxxxxxx > > To unsubscribe send an email to ceph-users-leave@xxxxxxx > > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |