in
nautilus as well, it was backported only to octopus. I have updated
accordingly.
On Fri, Nov 13, 2020 at 1:24 PM Neha Ojha <nojha(a)redhat.com> wrote:
https://tracker.ceph.com/issues/48230#note-2 is what seems to be the
problem, though I don't understand it fully yet, could be related to
https://github.com/ceph/ceph/pull/37844.
On Fri, Nov 13, 2020 at 12:24 PM Dan Mick <dmick(a)redhat.com> wrote:
>
> On 11/13/2020 12:18 PM, Patrick Donnelly wrote:
> > On Fri, Nov 13, 2020 at 11:56 AM Neha Ojha <nojha(a)redhat.com> wrote:
> >>
> >> On Fri, Nov 13, 2020 at 11:50 AM Patrick Donnelly
<pdonnell(a)redhat.com> wrote:
> >>>
> >>> On Fri, Nov 13, 2020 at 11:10 AM Yuri Weinstein
<yweinste(a)redhat.com> wrote:
> >>>>
> >>>> Details of this release summarized here:
> >>>>
https://tracker.ceph.com/issues/48200#note-1
> >>>>
> >>>> Asking dev leads for early approval as we target the release date
-
> >>>> early next week.
> >>>> Some suites are still in progress (will try to finish over the
weekend)
> >>>>
> >>>> rados - approved Neha?
> >>
> >> approved
> >>
> >>>> rgw - approved Casey?
> >>>> rbd - approved Jason?
> >>>> krbd - approved Jason, Ilya?
> >>>> fs - approved Patrick?
> >>>
> >>> We now have a warning in the cluster log about mgr modules failing:
> >>>
> >>> "2020-11-12 23:11:43.631135 mon.b (mon.0) 100 : cluster [ERR]
Health
> >>> check failed: 3 mgr modules have failed (MGR_MODULE_ERROR)" in
cluster
> >>> log
> >>>
> >>> From:
https://pulpito.ceph.com/yuriw-2020-11-12_20:43:15-fs-nautilus-distro-basic…
> >>>
> >>> e.g.:
/ceph/teuthology-archive/yuriw-2020-11-12_20:43:15-fs-nautilus-distro-basic-smithi/5617317/remote/smithi045/log/ceph-mgr.x.log.gz
> >>>
> >>> I don't see why this warning is happening. The modules in question
> >>> look like they have loaded successfully.
> >>
> >>
https://tracker.ceph.com/issues/48230 - this is appearing in RADOS
> >> too, but I think it is harmless
> >
> > It does look harmless but do we know why it's happening though?
> >
>
> It's odd, because the mgr log for the job cited in the bug shows a lot
> of what look like normal status messages from rbd_support (at least)
>