[Gluster-users] Possibly missing two steps in upgrade to 4.1 guide

[Hu Bert]

today i tested an upgrade 3.12.12 -> 4.1.2, and the glustereventsd
service was restarted. We use debian stretch; maybe it depends on the
operating system?

2018-08-21 16:17 GMT+02:00 mabi <mabi at protonmail.ch>:
> Oops missed that part at the bottom, thanks Hu Bert!
>
> Now the only thing missing from the upgrade guide is what to do about the glustereventsd service during the upgrade.
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On August 21, 2018 4:11 PM, Hu Bert <revirii at googlemail.com> wrote:
>
>> I think point 2 is already covered by the guide; see: "Upgrade
>> procedure for clients"
>>
>> Following are the steps to upgrade clients to the 4.1.x version,
>>
>> NOTE: x is the minor release number for the release
>>
>> > > > Unmount all glusterfs mount points on the client
>>
>> Stop all applications that access the volumes via gfapi (qemu, etc.)
>> Install Gluster 4.1
>>
>> > > > Mount all gluster shares
>>
>> Start any applications that were stopped previously in step (2)
>>
>> 2018-08-21 15:33 GMT+02:00 mabi mabi at protonmail.ch:
>>
>> > Hello,
>> > I just upgraded from 4.0.2 to 4.1.2 using the official documentation:
>> > https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/
>> > I noticed that this documentation might be missing the following two additional steps:
>> >
>> > 1.  restart the glustereventsd service
>> > 2.  umount and mount again gluster fuse mounts on clients after upgrading the clients (if using glusterfs fuse mounts of course)
>> >
>> > Best regards,
>> > M.
>> >
>> > Gluster-users mailing list
>> > Gluster-users at gluster.org
>> > https://lists.gluster.org/mailman/listinfo/gluster-users
>
>