6:40 p.m.
P.S. When creating a host, "Choose hosted engine deployment action" was set
to "deploy".
- Gilboa
On Thu, Dec 24, 2020 at 4:53 PM Gilboa Davara <gilboad(a)gmail.com> wrote:
Hello all,
Found the problem (at least I think so), but not the solution.
As I have an existing Gluster setup (quite complex one) this was the first
time I didn't use the "Hyperconverged gluster wizard" (via cockpit), but
used the "hosted-engine --deploy" cli instead (which I usually use to
deploy single host setups).
The idea being: Deploy the first hosts (via cli) and then add the two
additional hosts via compute->host->create.
For some odd reason I seem to remember this method was an approved way of
deploying an hyperconverged gluster setup, in cases you don't want to let a
wizard create the gluster bricks. Am I wrong?
A. In case I'm wrong: How can I deploy a 3 host hyperconverged setup,
_while_ using the preexisting gluster bricks (data/export/iso)?
B. I did a clean redeploy (via cockpit -> hosted engine -> hosted engine
deploy) and the cluster version is still 4.4 (and given the fact it only
deploys a single host, there's no way to upgrade it to 4.5, as I cannot put
the host into maintenance and I cannot add additional hosts).
- Gilboa
On Thu, Dec 24, 2020 at 12:50 PM Strahil Nikolov <hunter86_bg(a)yahoo.com>
wrote:
> Are you sure you have installed them with HE support ?
>
> Best Regards,
> Strahil Nikolov
> В 19:06 +0200 на 23.12.2020 (ср), Gilboa Davara написа:
>
>
> On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara <gilboad(a)gmail.com> wrote:
>
>
>
> On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad(a)gmail.com> wrote:
>
> On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo(a)redhat.com>
> wrote:
>
>
>
> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad(a)gmail.com>
> ha scritto:
>
> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina(a)redhat.com> wrote:
>
>
>
> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad(a)gmail.com> wrote:
>
> Thanks for the prompt reply.
> I assume I can safely ignore the "Upgrade cluster compatibility" warning
> until libvirt 6.6 gets pushed to CentOS 8.3?
>
>
> We are working on releasing AV 8.3, hopefully it will be available soon,
> but until that happen you have no way how to upgrade to CL 4.5 and you just
> need to stay in 4.4
>
>
> Understood.
>
> Thanks again.
> - Gilboa
>
>
>
> Just updating that oVirt 4.4.4 released yesterday comes with Advanced
> Virtualization 8.3 so you can now enable CL 4.5.
>
>
> Sadly enough, even post-full-upgrade (engine + hosts) something seems to
> be broken.
>
> In the WebUI, I see all 3 hosts marked as "up".
> But when I run hosted-engine --vm-status (or migrate the hosted engine),
> only the first (original deployed) host is available.
> I tried "reinstalling" (from the WebUI) the two hosts, no errors, no
> change.
> I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts)
> upgrade is successful; hosts1 fails (cannot migrate the hosted engine).
>
> Any idea what's broken?
>
> - Gilboa
>
>
>
> I'll remove the problematic hosts, re-add them, and reconfigure the
> network(s). Let's see if it works.
>
> - Gilboa
>
>
>
> Sorry for the noise. No go.
> Cleaned up the hosts via ovirt-hosted-engine-cleanup + reboot, tried
> "adding" them again, to no avail.
> Host marked as "up" in WebUI, network correctly configured, however,
> hosted-engine.conf isn't being created (see log below),
> ovirt-ha-broker/agent services cannot start and vm-status only shows one
> host.
>
> - Gilboa
>
> _______________________________________________
>
> Users mailing list --
>
> users(a)ovirt.org
>
>
> To unsubscribe send an email to
>
> users-leave(a)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/2JEBBBCTAB5...
>
>
>