Re: [ceph-users] Active MON aborts on Jewel 10.2.2 with FAILED assert(info.state == MDSMap::STATE_STANDBY

Just for giggles I tried the rolling upgrade to 10.2.2 again today. This time I rolled mon.0 and osd.0 first while keeping the mds servers up and then rolled them before moving on to the other three. No assertion failure this time since I guess I always had an mds active. I wonder if I will

Re: [ceph-users] Active MON aborts on Jewel 10.2.2 with FAILED assert(info.state == MDSMap::STATE_STANDBY

Manual downgrade to 10.2.0 put me back in business. I'm going to mask 10.2.2 and then try to let 10.2.1 emerge. Bill Sharer On 07/06/2016 02:16 PM, Bill Sharer wrote: I noticed on that USE list that the 10.2.2 ebuild introduced a new cephfs emerge flag, so I enabled that and emerged

Re: [ceph-users] Active MON aborts on Jewel 10.2.2 with FAILED assert(info.state == MDSMap::STATE_STANDBY

I noticed on that USE list that the 10.2.2 ebuild introduced a new cephfs emerge flag, so I enabled that and emerged everywhere again. The active mon is still crashing on the assertion though. Bill Sharer On 07/05/2016 08:14 PM, Bill Sharer wrote: Relevant USE flags FWIW # emerge -pv

Re: [ceph-users] Active MON aborts on Jewel 10.2.2 with FAILED assert(info.state == MDSMap::STATE_STANDBY

Relevant USE flags FWIW # emerge -pv ceph These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ~] sys-cluster/ceph-10.2.2::gentoo USE="fuse gtk jemalloc ldap libaio libatomic nss radosgw static-libs xfs -babeltrace -cephfs -cryptopp

Re: [ceph-users] Active MON aborts on Jewel 10.2.2 with FAILED assert(info.state == MDSMap::STATE_STANDBY

Thanks for the report; created a ticket and somebody will get on it shortly. http://tracker.ceph.com/issues/16592 -Greg On Sun, Jul 3, 2016 at 5:55 PM, Bill Sharer wrote: > I was working on a rolling upgrade on Gentoo to Jewel 10.2.2 from 10.2.0. > However now I can't

[ceph-users] Active MON aborts on Jewel 10.2.2 with FAILED assert(info.state == MDSMap::STATE_STANDBY

I was working on a rolling upgrade on Gentoo to Jewel 10.2.2 from 10.2.0. However now I can't get a monitor quorum going again because as soon as I get one, the mon which wins the election blows out with an assertion failure. Here's my status at the moment kroll110.2.2ceph mon.0