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

[mabi]

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.

[Hu Bert]

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

Post by mabi

Unmount all glusterfs mount points on the client

Stop all applications that access the volumes via gfapi (qemu, etc.)
Install Gluster 4.1

Post by mabi

Mount all gluster shares

Start any applications that were stopped previously in step (2)

Post by mabi
Hello,
https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/
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
https://lists.gluster.org/mailman/listinfo/gluster-users

[mabi]

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 ‐‐‐‐‐‐‐

Post by Hu Bert
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

Post by mabi

Unmount all glusterfs mount points on the client

Stop all applications that access the volumes via gfapi (qemu, etc.)
Install Gluster 4.1

Post by mabi

Mount all gluster shares

Start any applications that were stopped previously in step (2)

Post by mabi
Hello,
https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/
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
https://lists.gluster.org/mailman/listinfo/gluster-users

[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?

Post by mabi
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 ‐‐‐‐‐‐‐

Post by Hu Bert
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

Post by mabi

Unmount all glusterfs mount points on the client

Stop all applications that access the volumes via gfapi (qemu, etc.)
Install Gluster 4.1

Post by mabi

Mount all gluster shares

Start any applications that were stopped previously in step (2)

Post by mabi
Hello,
https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/
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
https://lists.gluster.org/mailman/listinfo/gluster-users

[mabi]

Funny I also use stretch but from 4.0.2 to 4.1.2 the glustereventsd did not get restarted automatically so I restarted it manually after having finished the upgrade.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

Post by 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?

Post by mabi
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 ‐‐‐‐‐‐‐

Post by Hu Bert
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

Post by mabi

Unmount all glusterfs mount points on the client

Stop all applications that access the volumes via gfapi (qemu, etc.)
Install Gluster 4.1

Post by mabi

Mount all gluster shares

Start any applications that were stopped previously in step (2)

Post by mabi
Hello,
https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/
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
https://lists.gluster.org/mailman/listinfo/gluster-users

[Shyam Ranganathan]

Post by mabi
Hello,
https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/
1) restart the glustereventsd service

Updates to the document submitted here [1], reviews welcome.

Thanks for reporting this.

Shyam

[1] https://github.com/gluster/glusterdocs/pull/410