Its really weird.
Just tried again, with the same failure, on a freshly reinstalled CentOS 8.
Server has a number of vlan interfaces, on a physical interface
enp2s0f1, all in the defined notation,
one vlan interface has an IP, 10.200.10.3/23,
Second physical interface enp2s0f0 is configured for 10.200.30.3/23,
is the interface with a gateway and DNS, and the router can provide
other IPs with DHCP here, and which I hope to have ovirtmgmt on.
I run hosted-engine --deploy, I select the gateway for the enp2s0f1
Please indicate the gateway IP address [10.200.30.1]: 10.200.10.1
Please indicate a nic to set ovirtmgmt bridge on (enp2s0f1,
enp2s0f1.1014, enp2s0f1.1016, enp2s0f1.1015, enp2s0f1.1005, enp2s0f0)
Please specify which way the network connectivity should be
checked (ping, dns, tcp, none) [dns]:dns
How should the engine VM network be configured? (DHCP,
Please enter the IP address to be used for the engine VM :
[ ERROR ] The Engine VM (10.200.30.10/32) and this host
(10.200.30.3/32) will not be in the same IP subnet.
Static routing configuration are not supported on automatic
What can I try differently?
On Wed, Oct 27, 2021 at 7:40 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote:
Prefix of '32' means that there are no other IPs in the subnet -> usually this
prefix is used in firewalls to indicate that the rule is only for that IP.
It doesn't seem legit to me.
'The Engine VM (10.200.30.5/32) and this host (10.200.30.3/32) will not be in the
same IP subnet.'
This happens when I select a static IP address configuration for the engine.
Ive been struggling with setting up ovirt-hosted-engine on CentOS 8 servers in the
Equinix network, using hosted-engine --deploy.
Why would the setup not want the engine and the host it's being setup on, not be in
the same subnet?
Can someone please help me understand what prerequisites I am missing?
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/