From: Nathan Cutler <ncutler@suse.cz>
To: Yuri Weinstein <yweinste@redhat.com>
Cc: Orit Wasserman <owasserm@redhat.com>,
Sage Weil <sweil@redhat.com>,
Tamilarasi Muthamizhan <tmuthami@redhat.com>,
Ilya Dryomov <idryomov@gmail.com>,
"Development, Ceph" <ceph-devel@vger.kernel.org>,
"Durgin, Josh" <jdurgin@redhat.com>,
"Just, Samuel" <sjust@redhat.com>,
"Dillaman, Jason" <dillaman@redhat.com>,
Gregory Farnum <gfarnum@redhat.com>,
John Spray <jspray@redhat.com>,
"Sadeh-Weinraub,
Yehuda" <yehuda@redhat.com>"ceph-devel@vger.kernel.org"
<ceph-devel@vger.kernel.org>
Subject: Re: hammer 0.94.10 QE status
Date: Fri, 17 Feb 2017 06:06:44 +0100 [thread overview]
Message-ID: <473edf7d-c46a-be4c-bc8a-35be4c095b2b@suse.cz> (raw)
In-Reply-To: <CAMMFjmFtrwGMaVweDt9eefWta22UdjgmdVg0it1t0SwWma_FXg@mail.gmail.com>
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.
next prev parent reply other threads:[~2017-02-17 5:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMMFjmHCAM6wmygytBDqwh89UOEex24_GGqrLJvXcOUS+QEg9A@mail.gmail.com>
2017-02-01 17:03 ` hammer 0.94.10 QE status Ilya Dryomov
2017-02-02 10:01 ` Ilya Dryomov
2017-02-02 11:17 ` Nathan Cutler
2017-02-07 21:47 ` Yuri Weinstein
2017-02-08 21:14 ` Yuri Weinstein
[not found] ` <CAObvjwPb_PosEnGOXP2tV4aWjnTyed7-275svyK+vu4uxYdTzQ@mail.gmail.com>
2017-02-13 16:24 ` Sage Weil
2017-02-14 14:30 ` Orit Wasserman
2017-02-14 15:04 ` Nathan Cutler
2017-02-14 17:46 ` Yuri Weinstein
2017-02-17 5:06 ` Nathan Cutler [this message]
2017-02-17 14:14 ` Sage Weil
2017-02-17 18:55 ` Gregory Farnum
2017-02-17 19:52 ` Nathan Cutler
2017-02-17 23:21 ` Gregory Farnum
2017-02-18 8:19 ` Nathan Cutler
2017-02-18 8:39 ` Nathan Cutler
2017-02-14 17:05 ` Yuri Weinstein
2017-02-01 19:12 ` John Spray
2017-02-01 16:55 Yuri Weinstein
2017-02-01 20:36 ` Sage Weil
2017-02-01 23:47 ` Vasu Kulkarni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=473edf7d-c46a-be4c-bc8a-35be4c095b2b@suse.cz \
--to=ncutler@suse.cz \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=gfarnum@redhat.com \
--cc=idryomov@gmail.com \
--cc=jdurgin@redhat.com \
--cc=jspray@redhat.com \
--cc=owasserm@redhat.com \
--cc=sjust@redhat.com \
--cc=sweil@redhat.com \
--cc=tmuthami@redhat.com \
--cc=yehuda@redhat.com \
--cc=yweinste@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.