On Mon, Feb 3, 2020 at 12:10 PM Vrgotic, Marko
wrote:
> Hi Dominik,
>
>
>
> Thank you – please find the sql query output file attached.
>
>
>
> In addition, today, while spawning set of VMs, and we are mostly using
> Ansible (98% of the time), we got this message:
>
> An exception occurred
On Fri, Jan 31, 2020 at 9:56 AM Vrgotic, Marko
wrote:
> Dear Yedidyah,
>
> We are actually seeing collisions, which is why I reached out in first
> place.
> Strange is that is did not happen since few weeks ago, and since then I
> saw it multiple times.
>
I am interested in reproducing this
Dear Yedidyah,
We are actually seeing collisions, which is why I reached out in first place.
Strange is that is did not happen since few weeks ago, and since then I saw it
multiple times.
For now I am simply going to create new mac pool for each of the clusters and
switch to it, hoping it's not
On Thu, Jan 23, 2020 at 2:30 PM Vrgotic, Marko
wrote:
>
> Hi Yedidyah,
>
> Thank you for you update.
>
> This platform started with 4.3 deployment.
> The Default mac address pool, apparently on all Clusters (5) is:
> from_mac | to_mac
> ---+---
>
Hi Yedidyah,
Thank you for you update.
This platform started with 4.3 deployment.
The Default mac address pool, apparently on all Clusters (5) is:
from_mac | to_mac
---+---
56:6f:ef:88:00:00 | 56:6f:ef:88:ff:ff
Interestingly enough, I am alos not
On Tue, Jan 21, 2020 at 2:30 PM Vrgotic, Marko
wrote:
>
> Dear oVirt,
>
>
>
> While investigating and DHCP & DDNS collision issues between two VM servers
> from different oVirt clusters, I noticed that oVirt assigns same default MAC
> range for each of it’s managed clusters.
Is this a new 4.3
6 matches
Mail list logo
