Many thanks. Happy new year.
- Gilboa
On Wed, Dec 30, 2020 at 9:12 PM Strahil Nikolov
wrote:
> Maybe there is a missing package that is preventing that.
> Let's see what the devs will find out next year (thankfully you wpn't have
> to wait much).
>
> Best Regards,
> Strahil Nikolov
>
>
>
>
>
>
Maybe there is a missing package that is preventing that.
Let's see what the devs will find out next year (thankfully you wpn't have to
wait much).
Best Regards,
Strahil Nikolov
В сряда, 30 декември 2020 г., 16:30:37 Гринуич+2, Gilboa Davara
написа:
Short update.
1. Ran
Engine log attached. (Looks clean)
- Gilboa
On Wed, Dec 30, 2020 at 4:30 PM Gilboa Davara wrote:
> Short update.
> 1. Ran ovirt-hosted-engine-cleanup on all 3 nodes.
> 2. Installed hosted engine on the first engine via hosted-engine --deploy
> (w/ gluster storage).
> 3. Added the two remaining
Short update.
1. Ran ovirt-hosted-engine-cleanup on all 3 nodes.
2. Installed hosted engine on the first engine via hosted-engine --deploy
(w/ gluster storage).
3. Added the two remaining hosts using host -> new -> w/ hosted engine ->
deploy.
4. All machines are up and running and I can see theme
On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov
wrote:
> Any hints in vdsm logs on the affected host or on the broker.log/agent.log
> ?
>
> Happy Hollidays to everyone!
>
> Best Regards,
> Strahil Nikolov
>
>
Hello,
Sorry for the late reply.
One of the nodes suffered a major failure and I'm
Any hints in vdsm logs on the affected host or on the
broker.log/agent.log ?
Happy Hollidays to everyone!
Best Regards,Strahil Nikolov
В 14:33 +0200 на 25.12.2020 (пт), Gilboa Davara написа:
> Hello,
>
> Reinstall w/ redeploy produced the same results.
>
> - Gilboa
>
>
> On Thu, Dec 24, 2020
Hello,
Reinstall w/ redeploy produced the same results.
- Gilboa
On Thu, Dec 24, 2020 at 8:07 PM Strahil Nikolov
wrote:
>
> I "forked" this email into a new subject ("Manually deploying a
> hyperconverged setup with an existing gluster bricks")
> But nevertheless, no idea if its intended or
> I "forked" this email into a new subject ("Manually deploying a
> hyperconverged setup with an existing gluster bricks")But
> nevertheless, no idea if its intended or not, but it seems that
> adding a host via "host->computer->create" doesn't create the
> necessary
On Thu, Dec 24, 2020 at 5:04 PM Gilboa Davara wrote:
> Hello,
>
> On Thu, Dec 24, 2020 at 12:45 PM Strahil Nikolov
> wrote:
>
>> 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
Hello,
On Thu, Dec 24, 2020 at 12:45 PM Strahil Nikolov
wrote:
> 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
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
> wrote:
> > On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara
> > wrote:
> > > On Tue, Dec 22, 2020 at 11:45 AM
> 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
On Wed, Dec 23, 2020 at 7:08 PM Gilboa Davara wrote:
>
>
> On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara wrote:
>>
>>
>>
>> On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara wrote:
>>>
>>> On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola
>>> wrote:
Il giorno mer 16 dic 2020
Hello,
If I understand the problem correctly , you are facing the problem of
migrating the HE VM,
If Yes, I suspect the issue is all the cores have been allocated to the HE
VM and because of this migration to other hosts not showing please verify
once with hypervisor available core to HE VM
On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara wrote:
>
>
> On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara wrote:
>
>> On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola
>> wrote:
>>
>>>
>>>
>>> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <
>>> gilb...@gmail.com> ha scritto:
>>>
On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara wrote:
> On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola
> wrote:
>
>>
>>
>> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara
>> ha scritto:
>>
>>> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina
>>> wrote:
>>>
On Wed, Dec 16,
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola
wrote:
>
>
> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara
> ha scritto:
>
>> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina wrote:
>>
>>>
>>>
>>> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara wrote:
>>>
Thanks for the prompt
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara
ha scritto:
> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina wrote:
>
>>
>>
>> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara wrote:
>>
>>> Thanks for the prompt reply.
>>> I assume I can safely ignore the "Upgrade cluster compatibility"
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina wrote:
>
>
> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara 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
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara 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
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?
- Gilboa
On Wed, Dec 16, 2020 at 5:56 PM Martin Perina wrote:
>
>
> On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara wrote:
>
>> Shani,
>>
>> 1. I
On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara wrote:
> Shani,
>
> 1. I created a new 4.5 cluster with the same CPU (Secure Intel Cascadelake
> Server Family) and platform type (Q35/BIOS).
> 2. All 3 hosts are 8.3, but report 4.4 compatibility.
> 3. The only reason I attempted to upgrade the
Shani,
1. I created a new 4.5 cluster with the same CPU (Secure Intel Cascadelake
Server Family) and platform type (Q35/BIOS).
2. All 3 hosts are 8.3, but report 4.4 compatibility.
3. The only reason I attempted to upgrade the cluster was simple: The
cluster state kept on dropping down to
Hi Gilboa,
Here are some guidelines/checks:
- Are you able to create a 4.5 DC/cluster?
- Host can be Up in the 4.5 clusters only when it reports 4.5 level
compatibility (it's based on RHEL 8.3).
Can you make sure that on all 3 hosts?
- You can upgrade the 4.4 clusters to 4.5 only when all
24 matches
Mail list logo
