Il giorno mar 5 nov 2019 alle ore 10:40 Nathanaël Blanchet
ha scritto:
> Hello,
>
> I'm interested by installing okd on ovirt with the official openshift
> installer (https://github.com/openshift/installer), but ovirt is not yet
> supported.
>
> Regarding
Hello,
I'm interested by installing okd on ovirt with the official openshift
installer (https://github.com/openshift/installer), but ovirt is not yet
supported.
Regarding https://bugzilla.redhat.com/show_bug.cgi?id=1578255 and
Best Regards,
Strahil Nikolov
On Nov 2, 2019 17:17, Strahil wrote:
I think I have a theory about ovirt1 , but I have to test it.
1. Ovirt1 has a team device controlled by NetworkManager , but in engine those
interfaces are unused
>What is your motivation to use a team device,
It's releated to all 3 nodes.I've created a vdsm hook in 'after_ifcfg_write'
that sets a 'DELAY=5' and 'STP=on' and after reboot everything is OK.
I have just completely powered off the lab and after powering on - the gateway
is OK, so it cannot be reproduced any longer.
Best Regards,Strahil
On Sat, Nov 2, 2019 at 4:59 PM Strahil wrote:
> Hi Dominik,
>
> I think I found it - it seems that for some reason my gateway is missing
> in 'ip route'.
> Running 'ifdown ovirtmgmt; ifup ovirtmgmt' fixes it, which proves that
> network scripts read properly the ifcfg-ovirtmgmt file.
>
> Do you
Hi Dominik,
I think I found it - it seems that for some reason my gateway is missing in 'ip
route'.
Running 'ifdown ovirtmgmt; ifup ovirtmgmt' fixes it, which proves that network
scripts read properly the ifcfg-ovirtmgmt file.
Do you have any idea where to look for?
Best Regards,
Strahil
I think I have a theory about ovirt1 , but I have to test it.
1. Ovirt1 has a team device controlled by NetworkManager , but in engine those
interfaces are unused
2. I guess that when I recently 'reinstalled' the host from UI, the old
teamports' ifcfg- was moved to ifcfg--1 and the
original
I saw the hint in the Cluster's tab and then on each host. I had to put the
host back to maintenance in order to sync it again.
Logs attached .
Best Regards,Strahil Nikolov
В четвъртък, 31 октомври 2019 г., 16:12:53 ч. Гринуич+2, Dominik Holler
написа:
On Thu, Oct 31, 2019 at 10:06
On Thu, Oct 31, 2019 at 10:06 AM Sandro Bonazzola
wrote:
>
>
> Il giorno gio 31 ott 2019 alle ore 09:45 Strahil Nikolov <
> hunter86...@yahoo.com> ha scritto:
>
>> Hi Sandro,
>>
>> I have just updated to latest release candidate (2 clusters in total - 1
>> AMD , 1 Intel).
>> The only issue
Il giorno gio 31 ott 2019 alle ore 09:45 Strahil Nikolov <
hunter86...@yahoo.com> ha scritto:
> Hi Sandro,
>
> I have just updated to latest release candidate (2 clusters in total - 1
> AMD , 1 Intel).
> The only issue observed is that after patching every host's ovirtmgmt (I
> have another one
Hi Sandro,
I have just updated to latest release candidate (2 clusters in total - 1 AMD ,
1 Intel).
The only issue observed is that after patching every host's ovirtmgmt (I have
another one that has none of the 4 roles which was OK) is out of sync and has
to be synced before removing
Il giorno mar 29 ott 2019 alle ore 04:58 Konstantin Shalygin
ha scritto:
> > The oVirt Project is pleased to announce the availability of the oVirt
> > 4.3.7 First Release Candidate for testing, as of October 18th, 2019.
>
> Sandro, thanks for announce. oVirt 4.3 still have "OpenStack Block
>
The oVirt Project is pleased to announce the availability of the oVirt
4.3.7 First Release Candidate for testing, as of October 18th, 2019.
Sandro, thanks for announce. oVirt 4.3 still have "OpenStack Block
Storage" provider support?
Because we want upgrade our oVirt 4.2.8 DC's and we use
13 matches
Mail list logo