Hi Stack,
Indeed this is a bug in the engine. We have opened a case [1] and are
working to fix it on 4.2 ASAP
Thanks for posting...
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1570388
Eitan
oVirt | Redhat
On Wed, Apr 18, 2018 at 8:35 PM, ~Stack~ wrote:
> On
On 04/18/2018 09:55 AM, ~Stack~ wrote:
> On 04/18/2018 08:41 AM, Eitan Raviv wrote:
>> Hi Stack,
>>
>> I read through your ordeal and I would like to post a few comments:
>
> Thanks I appreciate it!
>
>> * When I try to reproduce your scenario with the second network set to
>> 'not
On 04/18/2018 09:55 AM, ~Stack~ wrote:
> On 04/18/2018 08:41 AM, Eitan Raviv wrote:
[snip]
>> but on my setup it can be resolved: initially the second
>> network is proclaimed missing and the host becomes non-operational,
>> with its interfaces disappearing from the engine as you
On 04/18/2018 08:41 AM, Eitan Raviv wrote:
> Hi Stack,
>
> I read through your ordeal and I would like to post a few comments:
Thanks I appreciate it!
> * When I try to reproduce your scenario with the second network set to
> 'not required' before on-boarding the second host, it is
Hi Stack,
I read through your ordeal and I would like to post a few comments:
- When I try to reproduce your scenario with the second network set to
'not required' before on-boarding the second host, it is processed and set
to 'up' by the engine without any hiccups or any errors in the
Greetings,
After a few days of trial, error, and madness - I *think* I found the
source of my problem. Or at least I can now replicate it reliably. These
are the basics of my speed-run-to-test-failures setup.
Fresh minimal install of Scientific Linux 7.4 on a physical host for my
engine. Add the
6 matches
Mail list logo