On 4/2/2018 6:55 AM, Alex K wrote:
First issue with fencing is solved per an earlier reply.
Second issue has also been solved earlier the way you outlined but I'm
wondering why oVirt can't use br0 as the ovirtmgmt interface instead?
What specific settings on br0 does it NOT like? Is there any provision
or flexibility to allow for custom defined bridges with oVirt?
I stumbled upon this page:
https://www.ovirt.org/documentation/how-to/networking/bonding-vlan-bridge/
and tried it but oVirt would have none of it.
After I let oVirt setup it's own bridges, I can see the settings it used
(below) but wondering what *specific* settings in the network scripts
does it not like?
Would like to know what we can and can't touch in the config files if we
need to tweak the setup in higher level environments.
Cheers,
Tom
1098 -rw-rw-r--. 1 root root 289 Mar 29 03:30 ifcfg-ovirtmgmt
127014 -rw-rw-r--. 1 root root 145 Mar 29 03:30 ifcfg-eth0
127022 -rw-rw-r--. 1 root root 145 Mar 29 03:30 ifcfg-eth1
127016 -rw-rw-r--. 1 root root 145 Mar 29 03:30 ifcfg-eth2
127029 -rw-rw-r--. 1 root root 145 Mar 29 03:30 ifcfg-eth3
3039 -rw-rw-r--. 1 root root 169 Mar 29 03:30 route-ovirtmgmt
3200 -rw-rw-r--. 1 root root 166 Mar 29 03:30 rule-ovirtmgmt
127032 -rw-rw-r--. 1 root root 199 Mar 31 00:35 ifcfg-bond0
222656 drwxr-xr-x. 2 root root 4096 Mar 31 00:39 .
[root@mdskvm-p01 network-scripts]# cat ifcfg-bond0
# Generated by VDSM version 4.20.23-1.el7.centos
DEVICE=bond0
BONDING_OPTS='mode=1 miimon=100'
BRIDGE=ovirtmgmt
MACADDR=78:e7:d1:8f:4d:26
ONBOOT=yes
MTU=1500
DEFROUTE=no
NM_CONTROLLED=no
IPV6INIT=no
[root@mdskvm-p01 network-scripts]#
[root@mdskvm-p01 network-scripts]#
[root@mdskvm-p01 network-scripts]#
[root@mdskvm-p01 network-scripts]# cat ifcfg-ovirtmgmt
# Generated by VDSM version 4.20.23-1.el7.centos
DEVICE=ovirtmgmt
TYPE=Bridge
DELAY=0
STP=off
ONBOOT=yes
IPADDR=192.168.0.60
NETMASK=255.255.255.0
GATEWAY=192.168.0.1
BOOTPROTO=none
MTU=1500
DEFROUTE=yes
NM_CONTROLLED=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
DNS1=192.168.0.224
DNS2=192.168.0.44
[root@mdskvm-p01 network-scripts]# cat route-ovirtmgmt
# Generated by VDSM version 4.20.23-1.el7.centos
0.0.0.0/0 via 192.168.0.1 dev ovirtmgmt table 3232235580
192.168.0.0/24 via 192.168.0.60 dev ovirtmgmt table 3232235580
[root@mdskvm-p01 network-scripts]# cat rule-ovirtmgmt
# Generated by VDSM version 4.20.23-1.el7.centos
from 192.168.0.0/24 prio 32000 table 3232235580
from all to 192.168.0.0/24 dev ovirtmgmt prio 32000 table 3232235580
[root@mdskvm-p01 network-scripts]#
Hi,
you need a second host so as power management to work.
Since you verified it with command line then adding a second host should
resolve this issue.
In regards to the interface, you need to remove the bridge interface as
instructed (make it a simple interface) then leave ovirt to configure it
ovirtmgmt bridge.
Alex
On Wed, Mar 28, 2018 at 9:17 AM, TomK <[email protected]
<mailto:[email protected]>> wrote:
Hey Guy's,
I've tested my ILO2 fence from the ovirt engine CLI and that works:
fence_ilo2 -a 192.168.0.37 -l <USER> --password="<SECRET>"
--ssl-insecure --tls1.0 -v -o status
The UI gives me:
Test failed: Failed to run fence status-check on host
'ph-host01.my.dom'. No other host was available to serve as proxy
for the operation.
Going to add a second host in a bit but anyway to get this working
with just one host? I'm just adding the one host to oVirt for some
POC we are doing atm but the UI forces me to adjust Power Management
settings before proceeding.
Also:
2018-03-28 02:04:15,183-04 WARN [org.ovirt.engine.core.bll.net
<http://org.ovirt.engine.core.bll.net>work.NetworkConfigurator]
(EE-ManagedThreadFactory-engine-Thread-335) [2d691be9] Failed to
find a valid interface for the management network of host
ph-host01.my.dom. If the interface br0 is a bridge, it should be
torn-down manually.
2018-03-28 02:04:15,184-04 ERROR
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-335) [2d691be9] Exception:
org.ovirt.engine.core.bll.network.NetworkConfigurator$NetworkConfiguratorException:
Interface br0 is invalid for management network
I've these defined as such but not clear what it is expecting:
[root@ph-host01 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 <http://127.0.0.1/8> scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq
master bond0 state UP qlen 1000
link/ether 78:e7:d1:8c:b1:ba brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc mq
master bond0 state DOWN qlen 1000
link/ether 78:e7:d1:8c:b1:ba brd ff:ff:ff:ff:ff:ff
4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc mq
master bond0 state DOWN qlen 1000
link/ether 78:e7:d1:8c:b1:ba brd ff:ff:ff:ff:ff:ff
5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc mq
master bond0 state DOWN qlen 1000
link/ether 78:e7:d1:8c:b1:ba brd ff:ff:ff:ff:ff:ff
21: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc
noqueue master br0 state UP qlen 1000
link/ether 78:e7:d1:8c:b1:ba brd ff:ff:ff:ff:ff:ff
inet6 fe80::7ae7:d1ff:fe8c:b1ba/64 scope link
valid_lft forever preferred_lft forever
23: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state
DOWN qlen 1000
link/ether fe:69:c7:50:0d:dd brd ff:ff:ff:ff:ff:ff
24: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP qlen 1000
link/ether 78:e7:d1:8c:b1:ba brd ff:ff:ff:ff:ff:ff
inet 192.168.0.39/23 <http://192.168.0.39/23> brd 192.168.1.255
scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::7ae7:d1ff:fe8c:b1ba/64 scope link
valid_lft forever preferred_lft forever
[root@ph-host01 ~]# cd /etc/sysconfig/network-scripts/
[root@ph-host01 network-scripts]# cat ifcfg-br0
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
IPADDR=192.168.0.39
NETMASK=255.255.254.0 <tel:255.255.254.0>
GATEWAY=192.168.0.1
ONBOOT=yes
DELAY=0
USERCTL=no
DEFROUTE=yes
NM_CONTROLLED=no
DOMAIN="my.dom nix.my.dom"
SEARCH="my.dom nix.my.dom"
HOSTNAME=ph-host01.my.dom
DNS1=192.168.0.224
DNS2=192.168.0.44
DNS3=192.168.0.45
ZONE=public
[root@ph-host01 network-scripts]# cat ifcfg-bond0
DEVICE=bond0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
NM_CONTROLLED=no
BONDING_OPTS="miimon=100 mode=2"
BRIDGE=br0
#
#
# IPADDR=192.168.0.39
# NETMASK=255.255.254.0 <tel:255.255.254.0>
# GATEWAY=192.168.0.1
# DNS1=192.168.0.1
[root@ph-host01 network-scripts]#
--
Cheers,
Tom K.
-------------------------------------------------------------------------------------
Living on earth is expensive, but it includes a free trip around the
sun.
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
--
Cheers,
Tom K.
-------------------------------------------------------------------------------------
Living on earth is expensive, but it includes a free trip around the sun.
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
