Description of problem: In order to handle Ceph entitlements, the dependency for Openvswitch is being removed from os-net-config. Images containing Opensvswitch will still be built for OSP deployments. A check must be done in os-net-config for the existence of Openvswitch when os-net-config is used to configure a OVS component, i.e. ovs_bridge, ovs_bond, which will now fail for Ceph nodes.
Environment: os-net-config-9.2.1-0.20180831234441.c79a3ba.el7ost.noarch [root@controller-2 ~]# ovs-vsctl show e6c9595e-571a-495b-98f2-f7e36e9dd04c Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br-ex Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "eth2" Interface "eth2" Port br-ex Interface br-ex type: internal Port phy-br-ex Interface phy-br-ex type: patch options: {peer=int-br-ex} Bridge br-baremetal Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "phy-br-bae2b5d8" Interface "phy-br-bae2b5d8" type: patch options: {peer="int-br-bae2b5d8"} Port "eth0" Interface "eth0" Port br-baremetal Interface br-baremetal type: internal Bridge br-tun Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port br-tun Interface br-tun type: internal Port "vxlan-ac11021e" Interface "vxlan-ac11021e" type: vxlan options: {df_default="true", in_key=flow, local_ip="172.17.2.21", out_key=flow, remote_ip="172.17.2.30"} Port "vxlan-ac110214" Interface "vxlan-ac110214" type: vxlan options: {df_default="true", in_key=flow, local_ip="172.17.2.21", out_key=flow, remote_ip="172.17.2.20"} Port "vxlan-ac110211" Interface "vxlan-ac110211" type: vxlan options: {df_default="true", in_key=flow, local_ip="172.17.2.21", out_key=flow, remote_ip="172.17.2.17"} Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port br-int Interface br-int type: internal Port int-br-ex Interface int-br-ex type: patch options: {peer=phy-br-ex} Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "int-br-bae2b5d8" Interface "int-br-bae2b5d8" type: patch options: {peer="phy-br-bae2b5d8"} Bridge br-isolated fail_mode: standalone Port "vlan20" tag: 20 Interface "vlan20" type: internal Port "vlan30" tag: 30 Interface "vlan30" type: internal Port "vlan50" tag: 50 Interface "vlan50" type: internal Port br-isolated Interface br-isolated type: internal Port "vlan40" tag: 40 Interface "vlan40" type: internal Port "eth1" Interface "eth1" ovs_version: "2.10.0" [root@controller-2 ~]# os-net-config -c /etc/os-net-config/config.json [root@controller-2 ~]# [root@controller-2 ~]# [root@controller-2 ~]# [root@controller-2 ~]# [root@controller-2 ~]# mv ovs-appctl ^C [root@controller-2 ~]# which ovs-appctl /bin/ovs-appctl [root@controller-2 ~]# mv /bin/ovs-appctl /bin/ovs-appctl_2 [root@controller-2 ~]# less /var/log/messages [root@controller-2 ~]# os-net-config -c /etc/os-net-config/config.json Traceback (most recent call last): File "/bin/os-net-config", line 10, in <module> sys.exit(main()) File "/usr/lib/python2.7/site-packages/os_net_config/cli.py", line 259, in main obj = objects.object_from_json(iface_json) File "/usr/lib/python2.7/site-packages/os_net_config/objects.py", line 47, in object_from_json return OvsBridge.from_json(json) File "/usr/lib/python2.7/site-packages/os_net_config/objects.py", line 593, in from_json fail_mode=fail_mode) File "/usr/lib/python2.7/site-packages/os_net_config/objects.py", line 522, in __init__ check_ovs_installed(self.__class__.__name__) File "/usr/lib/python2.7/site-packages/os_net_config/objects.py", line 218, in check_ovs_installed raise InvalidConfigException(msg) os_net_config.objects.InvalidConfigException: OvsBridge cannot be created as OpenvSwitch is not installed.
The error in comment#5 is the expected output. Verifying the bug.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045