I followed the same steps as done by Jayme and I've double checked with infra
also, there is no issue with infra. Why does gluster peer status shows
disconnected after it gets upgraded?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an
On Tue, Oct 1, 2019 at 8:09 PM Jayme wrote:
> Hello,
>
> I am running oVirt 4.3.6 and glusterd service and peers on all HCI nodes
> are connected and working properly after updating. I'm not sure if I
> understand what your question or issue is. It definitely should be safe to
> update your
Hello,
I am running oVirt 4.3.6 and glusterd service and peers on all HCI nodes
are connected and working properly after updating. I'm not sure if I
understand what your question or issue is. It definitely should be safe to
update your oVirt HCI to 4.3.6. GlusterFS is able to update from 5.6
On Tue, Oct 1, 2019 at 6:00 PM Jayme 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.
esday, October 1, 2019, 5:01 PM
To: Anton Marchukov; Gobinda Das; Sundaramoorthi, Satheesaran; Sahina Bose
Cc: users; Akshita Jain
Subject: Re: [ovirt-users] Fwd: Unable to Upgrade
Il giorno mar 1 ott 2019 alle ore 11:27 Anton Marchukov
mailto:amarc...@redhat.com>> ha scritto:
Forwarding to
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
Il giorno mar 1 ott 2019 alle ore 11:27 Anton Marchukov
ha scritto:
> Forwarding to the users list.
>
> Begin forwarded message:
>
> *From: *"Akshita Jain"
> *Subject: **Unable to Upgrade*
> *Date: *1 October 2019 at 11:12:58 CEST
> *To: *in...@ovirt.org
>
> After upgrading oVirt 4.3.4 to
7 matches
Mail list logo
