[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-05-02 Thread José Ferradeira via Users
I just commented out this line on cli.py and it worked # value [ 'stripeCount' ] = el . find ( 'stripeCount' ). text De: "Nir Soffer" Para: "Alessandro De Salvo" Cc: "users" Enviadas: Sexta-feira, 29 De Abril de 2022 0:39:49 Assunto: [ovirt-users] Re: Issu

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-05-01 Thread Patrick Hibbs
This bug also affects non-hyperconverged Gluster volumes run by Debian hosts. (Debian uses Gluster 9. Specifically glusterfs-server 9.2-1.) Funnily enough, Gluster 9 is compatible with both oVirt 4.4 and 4.5. With no changes required on the Gluster side at all. So it seems that this bug is purely

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-04-28 Thread Nir Soffer
On Tue, Apr 26, 2022 at 12:47 PM Alessandro De Salvo wrote: > > Hi, > > the error with XML and gluster is the same I reported with a possible fix in > vdsm in another thread. > > The following fix worked for me, i.e. replacing the following line in >

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-04-28 Thread Abe E
If I wanted to rebuild that single node, what's the best way. Since it is up, I assume I can rebuild the partition using the below config then resetting the brick from engine? vgname: gluster_vg_sda pvname /dev/sda4 lvname gluster_lv_engine vgname:gluster_vg_sda path /gluster_bricks/engine

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-04-28 Thread Strahil Nikolov via Users
You might have other issues. Get a rescue media and check if you can activate the VG and mount the brick(s). Usually I prefer using systemd mount units which even if fail - won't block the boot process. Best Regards,Strahil Nikolov On Tue, Apr 26, 2022 at 19:58, Abe E wrote: That did

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-04-28 Thread Strahil Nikolov via Users
PR can be open against https://github.com/oVirt/vdsm Best Regards,Strahil Nikolov On Tue, Apr 26, 2022 at 12:49, Alessandro De Salvo wrote: ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-04-26 Thread Abe E
That did the trick for those nodes that wouldn't connect to the gluster, thank you! For the issue with the Gluster Node itself booting to emergency mode, it did not make a difference. The error in emergency mode says dependency failed for /gluster_bricks/data Subject: Unit

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-04-26 Thread Alessandro De Salvo
Hi, the error with XML and gluster is the same I reported with a possible fix in vdsm in another thread. The following fix worked for me, i.e. replacing the following line in /usr/lib/python3.6/site-packages/vdsm/gluster/cli.y 429c429 < if (el.find('stripeCount')):

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-04-26 Thread Sandro Bonazzola
@Gobinda Das can you please have a look? Il giorno mar 26 apr 2022 alle ore 06:47 Abe E ha scritto: > Hey All, > > I am having an issue upgrading from 4.4 to 4.5. > My setup > 3 Node Gluster (Cluster 1) + 3 Node Cluster (Cluster 2) > > If i recall the process correctly, the process I did last

[ovirt-users] Re: Issue upgrading 4.4 to 4.5 Gluster HCG

2022-04-25 Thread Abe E
Also, I checked for the postgresql-jdbc version on engine and it did not upgrade, it is on 42.2.3. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: