Hi,
On 12/19/2016 09:58 PM, Ken Dreyer wrote:
> I looked into this again on a Trusty VM today. I set up a single
> mon+osd cluster on v10.2.3, with the following:
>
> # status ceph-osd id=0
> ceph-osd (ceph/0) start/running, process 1301
>
> #ceph daemon osd.0 version
> {"version":"10.2.3"}
>
> I ran "apt-get upgrade" to get go 10.2.3 -> 10.2.5, and the OSD PID
> (1301) and version from the admin socket (v10.2.3) remained the same.
>
> Could something else be restarting the daemons in your case?
As Christian said, this is not _exactly_ the "problem" I have described
in my first message. You can read it again, I give _verbatim_ the commands
I launch in the host during an upgrade. Personally, I stop manually the
daemons before the "ceph" upgrade (which is not the case in your example
above):
1. I stop manually all OSD daemons in the host.
2. I make the "ceph" upgrade (sudo apt-get update && sudo apt-get upgrade)
Then...
3(i). Before the 10.2.5 version, the ceph daemons are still stopped.
3(ii). With the 10.2.5 version, the ceph daemons have been started automatically.
Personally I would prefer the 3i scenario (all details are in my first message).
I don't know what exactly but something has changed with the version 10.2.5.
Regards.
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
