Ah, must be more fixed than I thought. I don’t have a NodeNG setup to examine, so I’m afraid I won’t have many more suggestions.
On May 13, 2019, at 11:29 AM, Jayme <jaymef@gmail.com> wrote:
I use node NG as well, I just updated to 4.3.3 two days ago and I'm on Gluster 5.5. Yum update on host node yields no updates available
On Mon, May 13, 2019 at 1:03 PM Darrell Budic <budic@onholyground.com <mailto:budic@onholyground.com>> wrote: Ovirt just pulls in the gluster5 repos, if you upgrade now you should get gluster 5.6 on your nodes. If you’re running them on centos, you can install centos-release-gluster6 to go to gluster6. Ovirt NodeNG is a different story, as you mention, but I believe you can still run an update on it to get the latest gluster version?
Those recommendations are based on my personal experience, but see also: https://bugzilla.redhat.com/show_bug.cgi?id=1683602 <https://bugzilla.redhat.com/show_bug.cgi?id=1683602> https://bugzilla.redhat.com/show_bug.cgi?id=1677319 <https://bugzilla.redhat.com/show_bug.cgi?id=1677319>
On May 13, 2019, at 10:47 AM, Andreas Elvers <andreas.elvers+ovirtforum@solutions.work <mailto:andreas.elvers+ovirtforum@solutions.work>> wrote:
Please note that I am running a hyper-converged NodeNG setup. I understand that upgrading single components is not really possible with a ovirt Node NG. And could probably break the datacenter upgrade path.
Could you point out some reference for your suggestions? Docs, Bug reports or the sorts?
I encountered serious issues with 5.3-5.5 (crashing bricks, multiple brick processes for the same brick causing disconnects and excessive heals). I had better luck with 5.6, although it’s not clear to me if the duplicate brick process issue is still present in that version. I finally jumped to 6 which has been more stable for me. I’d recommend upgrading at least to 5.6 if not going right to 6.1.
Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/BFOB6QEST6EAGE... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/BFOB6QEST6EAGEZGSCM4GO7BFRUYCKEI/>
_______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5HKFS376DJVADI... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/5HKFS376DJVADIICLLVJSRJKXE73EBZC/>