For those that may come across this thread with the same issues ive been
encountering, I found a workaround to my related NAT issue (use at your own
risk).
1. I included the setup of the bridge in the ovirt kickstart, due to the
differences in hardware ill be dealing with I turned off Consisten
> On Thu, 11 Oct 2018 16:00:37 -
> "Brad Riemann" wrote:
>
>
> Ack, host behind the nat does not work, the IP address of NIC or bridge
> on the node has to match the IP address used to add the node in Engine.
>
>
> No, but the initial setup fails to detect the NIC or bridge to
> configure.
On Thu, 11 Oct 2018 16:00:37 -
"Brad Riemann" wrote:
> > On Wed, 10 Oct 2018 16:27:38 -
> > "Brad Riemann" wrote:
> >
> >
> > This is correct.
> >
> >
> > The physical interface (or bridge) which has the IP address used to add
> > the host is used for ovirtmgmt during the initial hos
> On Wed, 10 Oct 2018 16:27:38 -
> "Brad Riemann" wrote:
>
>
> This is correct.
>
>
> The physical interface (or bridge) which has the IP address used to add
> the host is used for ovirtmgmt during the initial host setup.
> For some reason oVirt does not detect the NIC or birdge which has
On Wed, 10 Oct 2018 16:27:38 -
"Brad Riemann" wrote:
> Hello again,
>
> I've been working on an automated solution that uses the API to add a host on
> first boot, the code checks out (or maybe it doesn't), however I can confirm
> that the ovirt engine works through adding all requirements
5 matches
Mail list logo
