Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

This fix is now merged into the kraken branch. On Sat, Feb 25, 2017 at 12:00 AM, David Disseldorp wrote: > Hi, > > On Thu, 23 Feb 2017 21:07:41 -0800, Schlacta, Christ wrote: > >> So hopefully when the suse ceph team get 11.2 released it should fix this, >> yes? > > Please raise a

Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

Hi, On Thu, 23 Feb 2017 21:07:41 -0800, Schlacta, Christ wrote: > So hopefully when the suse ceph team get 11.2 released it should fix this, > yes? Please raise a bug at bugzilla.opensuse.org, so that we can track this for the next openSUSE maintenance update. Cheers, David

Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

On Fri, Feb 24, 2017 at 3:07 PM, Schlacta, Christ wrote: > So hopefully when the suse ceph team get 11.2 released it should fix this, > yes? Definitely not a question I can answer. What I can tell you is the fix is only in master atm, not yet backported to kraken

Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

So hopefully when the suse ceph team get 11.2 released it should fix this, yes? On Feb 23, 2017 21:06, "Brad Hubbard" wrote: > Kefu has just pointed out that this has the hallmarks of > https://github.com/ceph/ceph/pull/13275 > > On Fri, Feb 24, 2017 at 3:00 PM, Brad

Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

Kefu has just pointed out that this has the hallmarks of https://github.com/ceph/ceph/pull/13275 On Fri, Feb 24, 2017 at 3:00 PM, Brad Hubbard wrote: > Hmm, > > What's interesting is the feature set reported by the servers has only > changed from > > e0106b84a846a42 > > Bit

Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

Hmm, What's interesting is the feature set reported by the servers has only changed from e0106b84a846a42 Bit 1 set Bit 6 set Bit 9 set Bit 11 set Bit 13 set Bit 14 set Bit 18 set Bit 23 set Bit 25 set Bit 27 set Bit 30 set Bit 35 set Bit 36 set Bit 37 set Bit 39 set Bit 41 set Bit 42 set Bit 48

Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

# begin crush map tunable choose_local_tries 0 tunable choose_local_fallback_tries 0 tunable choose_total_tries 50 tunable chooseleaf_descend_once 1 tunable chooseleaf_vary_r 1 tunable straw_calc_version 1 tunable allowed_bucket_algs 54 # devices device 0 osd.0 device 1 osd.1 device 2 osd.2 #

Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

Did you dump out the crushmap and look? On Fri, Feb 24, 2017 at 1:36 PM, Schlacta, Christ wrote: > insofar as I can tell, yes. Everything indicates that they are in effect. > > On Thu, Feb 23, 2017 at 7:14 PM, Brad Hubbard wrote: >> Is your change

Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

insofar as I can tell, yes. Everything indicates that they are in effect. On Thu, Feb 23, 2017 at 7:14 PM, Brad Hubbard wrote: > Is your change reflected in the current crushmap? > > On Fri, Feb 24, 2017 at 12:07 PM, Schlacta, Christ > wrote: >>

Re: [ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

Is your change reflected in the current crushmap? On Fri, Feb 24, 2017 at 12:07 PM, Schlacta, Christ wrote: > -- Forwarded message -- > From: Schlacta, Christ > Date: Thu, Feb 23, 2017 at 6:06 PM > Subject: Re: [ceph-users] Upgrade Woes

[ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

-- Forwarded message -- From: Schlacta, Christ Date: Thu, Feb 23, 2017 at 6:06 PM Subject: Re: [ceph-users] Upgrade Woes on suse leap with OBS ceph. To: Brad Hubbard So setting the above to 0 by sheer brute force didn't work, so it's

[ceph-users] Fwd: Upgrade Woes on suse leap with OBS ceph.

-- Forwarded message -- From: Schlacta, Christ Date: Thu, Feb 23, 2017 at 5:56 PM Subject: Re: [ceph-users] Upgrade Woes on suse leap with OBS ceph. To: Brad Hubbard They're from the suse leap ceph team. They maintain ceph, and build