I got that sorted out.
I had to re-create the MON data directory on this node, and this seems to have
been enough, even if not trivial.
I'm not sure if it helped that I destroyed cephfs (not yet used) and the MDS
daemons... I was lulcky I could do that.
/lesson learned : upgrade MONs first/
jet : Re: [ceph-users] jewel upgrade : MON unable to start
Why do you upgrade osds first if it is necessary to upgrade mons before
everything else?
On May 2, 2016 5:31:43 PM GMT+03:00, SCHAER Frederic
wrote:
>Hi,
>
>I'm < sort of > following the upgrade instructions on CentOS 7
Why do you upgrade osds first if it is necessary to upgrade mons before
everything else?
On May 2, 2016 5:31:43 PM GMT+03:00, SCHAER Frederic
wrote:
>Hi,
>
>I'm < sort of > following the upgrade instructions on CentOS 7.2.
>I upgraded 3 OSD nodes without too many issues, even if I would rewrite
Hi,
I'm < sort of > following the upgrade instructions on CentOS 7.2.
I upgraded 3 OSD nodes without too many issues, even if I would rewrite those
upgrade instructions to :
#chrony has ID 167 on my systems... this was set at install time ! but I use
NTP anyway.
yum remove chrony
sed -i -e '
