Il giorno mar 1 ott 2019 alle ore 11:27 Anton Marchukov < amarchuk(a)redhat.com&gt; ha scritto: > Forwarding to the users list. > > Begin forwarded message: > > *From: *"Akshita Jain" <akshita(a)councilinfosec.org&gt; > *Subject: **Unable to Upgrade* > *Date: *1 October 2019 at 11:12:58 CEST > *To: *infra(a)ovirt.org > > After upgrading oVirt 4.3.4 to 4.3.6, the gluster is also upgrading from > 5.6 to 6.5. But as soon as it upgrades gluster peer status shows > disconnected. > What is the correct method to upgrade oVirt with gluster HCI environment? > > +Gobinda Das <godas(a)redhat.com&gt; , +Sundaramoorthi, Satheesaran <sasundar(a)redhat.com&gt; , +Sahina Bose <sabose(a)redhat.com&gt; can you please follow up on this question? > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/24D6NKVLMYQ... > > > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat > > > > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/YO2RYKFDCSP... > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>* _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLYFAJS73RR...

On Tue, Oct 1, 2019 at 6:00 PM Jayme <jaymef(a)gmail.com&gt; wrote: > In an oVirt HCI gluster configuration you should be able to take down at > least one host at a time. The procedure I use to upgrade my oVirt HCI > cluster goes something like this: > > 1. Upgrade the oVirt engine setup packages. Upgrade the engine. Yum > update and reboot. > 2. Place the first host in maintenance mode and upgrade the host. > Reboot. Wait until the host is active and gluster bricks are fully healed. > 3. Place the next host in maintenance and perform the same steps until > all hosts are upgraded. > > *From: *"Akshita Jain" <akshita(a)councilinfosec.org&gt; >>> *Subject: **Unable to Upgrade* >>> *Date: *1 October 2019 at 11:12:58 CEST >>> *To: *infra(a)ovirt.org >>> >>> After upgrading oVirt 4.3.4 to 4.3.6, the gluster is also upgrading >>> from 5.6 to 6.5. But as soon as it upgrades gluster peer status shows >>> disconnected. >>> What is the correct method to upgrade oVirt with gluster HCI >>> environment? >>> >>> Hello Akshita, Jayme's steps are perfect enough for the update. If you see post updating to oVirt 4.3.6, your peers are in disconnected state, could you confirm that glusterd service is up and running on all HCI nodes ( # systemctl status glusterd ). Meanwhile, I can also try for the quick update from gluster-5.6 to 6.5 and update the results here. -- Satheesaran S ( sas )