From: Nathan Cutler <ncutler-AlSwsSmVLrQ@public.gmane.org>
To: Oliver Freyermuth
<freyermuth-PRwTpj6vllKyLsESG3L8NIQuADTiUCJX@public.gmane.org>,
ceph.novice-k4R3PER4nllwCEqMux5wBA@public.gmane.org
Cc: ceph-users <ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>,
Peter Wienemann
<wienemann-PRwTpj6vllKyLsESG3L8NIQuADTiUCJX@public.gmane.org>,
Ceph Development
<ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: HELP! --> CLUSER DOWN (was "v13.2.1 Mimic released")
Date: Mon, 30 Jul 2018 10:54:18 +0200 [thread overview]
Message-ID: <c0ca6365-93d3-ddcb-1260-52bae8209893@suse.cz> (raw)
In-Reply-To: <df40714b-4dd4-06cc-b104-d70b9f3d3536-PRwTpj6vllKyLsESG3L8NIQuADTiUCJX@public.gmane.org>
> for all others on this list, it might also be helpful to know which setups are likely affected.
> Does this only occur for Filestore disks, i.e. if ceph-volume has taken over taking care of these?
> Does it happen on every RHEL 7.5 system?
It affects all OSDs managed by ceph-disk on all RHEL systems (but not on
CentOS), regardless of whether they are filestore or bluestore.
> We're still on 13.2.0 here and ceph-detect-init works fine on our CentOS 7.5 systems (it just echoes "systemd").
> We're on Bluestore.
> Should we hold off on an upgrade, or are we unaffected?
The regression does not affect CentOS - only RHEL.
Nathan
next prev parent reply other threads:[~2018-07-30 8:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 19:25 v13.2.1 Mimic released Sage Weil
[not found] ` <086B2EB1-4349-4694-856C-ECA50FBF6211@godaddy.com>
[not found] ` <086B2EB1-4349-4694-856C-ECA50FBF6211-SMpshsswsndBDgjK7y7TUQ@public.gmane.org>
2018-07-28 14:46 ` HELP! --> CLUSER DOWN (was "v13.2.1 Mimic released") ceph.novice-k4R3PER4nllwCEqMux5wBA
2018-07-28 14:49 ` Sage Weil
[not found] ` <422702b2-35c6-413e-bb9f-506921ccb3fc-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2018-07-28 21:35 ` ceph.novice-k4R3PER4nllwCEqMux5wBA
2018-07-29 1:02 ` ceph.novice-k4R3PER4nllwCEqMux5wBA
2018-07-29 1:15 ` Vasu Kulkarni
[not found] ` <CAKPXa=ZLDi17fnf5gq0RfGPp_RGoFWQ7EutbqPuJ7OoJte=G_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-07-29 9:16 ` ceph.novice-k4R3PER4nllwCEqMux5wBA
2018-07-29 18:33 ` Nathan Cutler
[not found] ` <7404124f-008d-744e-9866-9a41ca88bd79-AlSwsSmVLrQ@public.gmane.org>
2018-07-30 7:50 ` ceph.novice-k4R3PER4nllwCEqMux5wBA
2018-07-30 8:44 ` Oliver Freyermuth
[not found] ` <df40714b-4dd4-06cc-b104-d70b9f3d3536-PRwTpj6vllKyLsESG3L8NIQuADTiUCJX@public.gmane.org>
2018-07-30 8:54 ` Nathan Cutler [this message]
[not found] ` <c0ca6365-93d3-ddcb-1260-52bae8209893-AlSwsSmVLrQ@public.gmane.org>
2018-07-30 8:59 ` Kenneth Waegeman
[not found] ` <7fcb4558-f426-54cd-2670-76c1d19e2496-Cru1EgDzd7c@public.gmane.org>
2018-07-30 11:07 ` Jake Grimmett
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=c0ca6365-93d3-ddcb-1260-52bae8209893@suse.cz \
--to=ncutler-alswssmvlrq@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org \
--cc=ceph.novice-k4R3PER4nllwCEqMux5wBA@public.gmane.org \
--cc=freyermuth-PRwTpj6vllKyLsESG3L8NIQuADTiUCJX@public.gmane.org \
--cc=wienemann-PRwTpj6vllKyLsESG3L8NIQuADTiUCJX@public.gmane.org \
/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.