We added a new collection in 17.2.1 to indicate Rook deployments, since we want to understand its volume in the wild, thus the module asks for re-opting-in. On Fri, Jun 24, 2022 at 9:52 AM Matthew Darwin <bugs@xxxxxxxxxx> wrote: > Thanks Yaarit, > > The cluster I was using is just a test cluster with a few OSD and > almost no data. Not sure why I have to re-opt in upgrading from 17.2.0 > to 17.2.1 > > On 2022-06-24 09:41, Yaarit Hatuka wrote: > > Hi Matthew, > > > > Thanks for your update. How big is the cluster? > > > > Thanks for opting-in to telemetry! > > Yaarit > > > > > > On Thu, Jun 23, 2022 at 11:53 PM Matthew Darwin <bugs@xxxxxxxxxx> wrote: > > > > Sorry. Eventually it goes away. Just slower than I was expecting. > > > > On 2022-06-23 23:42, Matthew Darwin wrote: > > > > > > I just updated quincy from 17.2.0 to 17.2.1. Ceph status reports > > > "Telemetry requires re-opt-in". I then run > > > > > > $ ceph telemetry on > > > > > > $ ceph telemetry on --license sharing-1-0 > > > > > > Still the message "TELEMETRY_CHANGED( Telemetry requires > > re-opt-in) > > > message" remains in the log. > > > > > > Any ideas how to get rid of this warning? There was no warning > > > before the upgrade. > > > > > _______________________________________________ > > 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 > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |