It seems I haven't learned my lesson with upgrading via GUI. For some reason my server crashed during use of the GUI Upgrade method and it looks like maybe it did not complete or the like. 3NodeGluster I then noticed that I had actually upgrading a single node to the 4.5.1 Testing Version, that being said my glusterfs for this node is on 10.2 while other nodes are on 10.1. Is there a "cleaner" way of reverting the upgrade? I assume there are other packages that may have been upgraded that should be reverted.
Downgrade is not recommended but as long as you didn't increase the Gluster Op version, you can downgrade the packages and restart the services. Another option is to reapply the last transaction. Best Regards,Strahil Nikolov On Sat, Jun 11, 2022 at 1:24, Abe E<aellahib@gmail.com> wrote: It seems I haven't learned my lesson with upgrading via GUI. For some reason my server crashed during use of the GUI Upgrade method and it looks like maybe it did not complete or the like. 3NodeGluster I then noticed that I had actually upgrading a single node to the 4.5.1 Testing Version, that being said my glusterfs for this node is on 10.2 while other nodes are on 10.1. Is there a "cleaner" way of reverting the upgrade? I assume there are other packages that may have been upgraded that should be reverted. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/LKL7PABR2ST5CH...
Thank You Strahil, I was actually able to use the node snapshot to revert a version back and get things going again. This time I'll wait till its completed its testing phase and maybe get a small lab to test the upgrade on, I need to remove the testing Repo as well, I was not aware that it was added/
If you use Gluster, don't forget to bump the OP version once you are happy with your tests.It controls the backward compatibility, but also some internal mechanisms and optimizations. Best Regards,Strahil Nikolov On Mon, Jun 13, 2022 at 19:54, Abe E<aellahib@gmail.com> wrote: Thank You Strahil, I was actually able to use the node snapshot to revert a version back and get things going again. This time I'll wait till its completed its testing phase and maybe get a small lab to test the upgrade on, I need to remove the testing Repo as well, I was not aware that it was added/ _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YJVADSIW2A3HL7...
All my Nodes are on the same version currently of 100000, are you saying its a good idea to do to be ready for any differences if I ever upgrade later on? Does the opversion correlate with the actual gluster version or does it just have to be higher than other nodes on lower versions? I ask because on glusterdocs is says if on ver 4 then you should set to gluster volume set all cluster.op-version 40000
participants (2)
-
Abe E -
Strahil Nikolov