[ceph-users] Re: 16.2.6 CEPHADM_REFRESH_FAILED New Cluster

2021-09-28 Thread Marco Pizzolo
Thank you very much Adam, Really appreciate it. On Mon, Sep 27, 2021 at 3:02 PM Adam King wrote: > Unfortunately, I can't think of a workaround that doesn't involve a code > change. I've created a tracker (https://tracker.ceph.com/issues/52745) > and am working towards a fix for this, but I'm n

[ceph-users] Re: 16.2.6 CEPHADM_REFRESH_FAILED New Cluster

2021-09-27 Thread Adam King
Unfortunately, I can't think of a workaround that doesn't involve a code change. I've created a tracker (https://tracker.ceph.com/issues/52745) and am working towards a fix for this, but I'm not sure how to deal with it using the current 16.2.6 image. Maybe others will have some ideas. On Mon, Sep

[ceph-users] Re: 16.2.6 CEPHADM_REFRESH_FAILED New Cluster

2021-09-27 Thread Marco Pizzolo
Good morning Adam, Ceph users, Is there something we can do to extend the acceptable response size? Trying to understand if there is some viable workaround that we can implement. Thanks, Marco On Fri, Sep 24, 2021 at 2:59 PM Marco Pizzolo wrote: > Hi Adam, > > I really appreciate your time rev

[ceph-users] Re: 16.2.6 CEPHADM_REFRESH_FAILED New Cluster

2021-09-24 Thread Adam King
It looks like the output from a ceph-volume command was too long to handle. If you run "cephadm ceph-volume -- inventory --format=json" (add "--with-lsm" if you've turned on device_enhanced_scan) manually on each host do any of them fail in a similar fashion? On Fri, Sep 24, 2021 at 1:37 PM Marco