From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Cutler Subject: Re: hammer 0.94.10 QE status Date: Fri, 17 Feb 2017 06:06:44 +0100 Message-ID: <473edf7d-c46a-be4c-bc8a-35be4c095b2b@suse.cz> References: <90f9fb1d-74fa-3ae0-e5b7-186e5d1b2638@suse.cz> <22868a53-b99e-0686-e7e1-a288558aed27@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de ([195.135.220.15]:53449 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750826AbdBQFGs (ORCPT ); Fri, 17 Feb 2017 00:06:48 -0500 In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Yuri Weinstein Cc: Orit Wasserman , Sage Weil , Tamilarasi Muthamizhan , Ilya Dryomov , "Development, Ceph" , "Durgin, Josh" , "Just, Samuel" , "Dillaman, Jason" , Gregory Farnum , John Spray , "Sadeh-Weinraub, Yehuda" "ceph-devel@vger.kernel.org" From re-reading this thread I determined that the only two outstanding issues are upgrade/firefly-x and rgw+centos (can anyone confirm?) I don't think upgrade/firefly-x should be a blocker. Rationale: as of the jewel release, firefly clusters were supposed to be upgraded to at least hammer. As of the kraken release, support of hammer has been focused on facilitating users to upgrade from hammer to jewel. In other words, firefly clusters should already have been upgraded and upgrading from firefly to hammer is no longer supported. As for the rgw valgrind/libtcmalloc failures on centos, I made a wip-hammer-baseline branch based on "hammer" but with a different SHA1 ("git commit --amend --reset-author") and pushed it to ceph/ceph-ci.git so Shaman will re-build it. This should ensure that "flavor=notcmalloc" really means what it says. Re-running rgw+centos on this wip-hammer-baseline branch will tell us more.