On Mon, Dec 3, 2018 at 5:00 PM Jan Kasprzak wrote:
>
> Dan van der Ster wrote:
> : It's not that simple see http://tracker.ceph.com/issues/21672
> :
> : For the 12.2.8 to 12.2.10 upgrade it seems the selinux module was
> : updated -- so the rpms restart the ceph.target.
> : What's worse is
Dan van der Ster wrote:
: It's not that simple see http://tracker.ceph.com/issues/21672
:
: For the 12.2.8 to 12.2.10 upgrade it seems the selinux module was
: updated -- so the rpms restart the ceph.target.
: What's worse is that this seems to happen before all the new updated
: files are in
There's also an additional issue which made us activate
CEPH_AUTO_RESTART_ON_UPGRADE=yes
(and of course, not have automatic updates of Ceph):
When using compression e.g. with Snappy, it seems that already running OSDs
which try to dlopen() the snappy library
for some version upgrades become
It's not that simple see http://tracker.ceph.com/issues/21672
For the 12.2.8 to 12.2.10 upgrade it seems the selinux module was
updated -- so the rpms restart the ceph.target.
What's worse is that this seems to happen before all the new updated
files are in place.
Our 12.2.8 to 12.2.10
Paul Emmerich wrote:
: Upgrading Ceph packages does not restart the services -- exactly for
: this reason.
:
: This means there's something broken with your yum setup if the
: services are restarted when only installing the new version.
Interesting. I have verified that I have
Upgrading Ceph packages does not restart the services -- exactly for
this reason.
This means there's something broken with your yum setup if the
services are restarted when only installing the new version.
Paul
--
Paul Emmerich
Looking for help with your Ceph cluster? Contact us at
