On 10/02/2021 06:54, Ales Musil wrote:
>
>
> On Tue, Feb 9, 2021 at 10:04 PM lejeczek via Users
> <users@ovirt.org <mailto:users@ovirt.org>> wrote:
>
>
>
>     On 09/02/2021 19:02, Strahil Nikolov wrote:
>     > Did you disable NetworkManager.service ?
>     >
>     > Best Regards,
>     > Strahil Nikolov
>     I do not guess that's possible. On Centos Steam, sevice
>     NetworkManager even if disabled is "pulled up" by vdsm
>     itself. Removing NetworkManager rpm package is also not
>     possible as oVirt or its dependencies require it.
>     Unless this is a bug, it seems that 4.4.5-master on
>     Centos
>     Stream works that way, differently.
>
>     regards, L.
>     _______________________________________________
>     Users mailing list -- users@ovirt.org
>     <mailto:users@ovirt.org>
>     To unsubscribe send an email to users-leave@ovirt.org
>     <mailto:users-leave@ovirt.org>
>     Privacy Statement:
>     https://www.ovirt.org/privacy-policy.html
>     <https://www.ovirt.org/privacy-policy.html>
>     oVirt Code of Conduct:
>     https://www.ovirt.org/community/about/community-guidelines/
>     <https://www.ovirt.org/community/about/community-guidelines/>
>     List Archives:
>     https://lists.ovirt.org/archives/list/users@ovirt.org/message/EX5YMMBVK7WD2ROGSK2DMZ6MM5734NYB/
>     <https://lists.ovirt.org/archives/list/users@ovirt.org/message/EX5YMMBVK7WD2ROGSK2DMZ6MM5734NYB/>
>
>
> Disabling NetworkManager would break all networking on the
> host because from 4.4
> this is the main provider for networking.
>
> Can you please also provide a line from supoervdsm.log
> that starts with "Desired state:"?
>
-> $ grep esired.stat -B8 -A8 /var/log/vdsm/supervdsm.log
MainProcess|jsonrpc/3::INFO::2021-02-09
15:04:19,520::hooks::122::root::(_runHooksDir)
/usr/libexec/vdsm/hooks/before_network_setup/50_fcoe: rc=0
err=b''
MainProcess|jsonrpc/3::INFO::2021-02-09
15:04:19,520::configurator::90::root::(_setup_nmstate)
Processing setup through nmstate
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,528::context::144::root::(register_async) Async
action: Retrieve applied config: ethernet ens3 started
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,528::context::144::root::(register_async) Async
action: Retrieve applied config: bridge virbr0 started
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,528::context::144::root::(register_async) Async
action: Retrieve applied config: tun vnet0 started
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,530::context::153::root::(finish_async) Async
action: Retrieve applied config: ethernet ens3 finished
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,530::context::153::root::(finish_async) Async
action: Retrieve applied config: bridge virbr0 finished
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,530::context::153::root::(finish_async) Async
action: Retrieve applied config: tun vnet0 finished
MainProcess|jsonrpc/3::INFO::2021-02-09
15:04:19,537::configurator::92::root::(_setup_nmstate)
Desired state: {'interfaces': [{'name': 'ens3', 'state':
'up', 'mtu': 1500, 'ipv4': {'enabled': False}, 'ipv6':
{'enabled': False}}, {'name': 'ovirtmgmt', 'type':
'linux-bridge', 'state': 'up', 'mtu': 1500, 'bridge':
{'port': [{'name': 'ens3'}], 'options': {'stp': {'enabled':
False}}}, 'ipv4': {'enabled': True, 'address': [{'ip':
'10.3.1.111', 'prefix-length': 24}], 'dhcp': False}, 'ipv6':
{'enabled': False}}], 'routes': {'config':
[{'next-hop-address': '10.3.1.254', 'next-hop-interface':
'ovirtmgmt', 'destination': '0.0.0.0/0', 'table-id': 0}]},
'dns-resolver': {'config': {'server': ['10.3.1.254']}}}
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,559::context::144::root::(register_async) Async
action: Retrieve applied config: ethernet ens3 started
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,559::context::144::root::(register_async) Async
action: Retrieve applied config: bridge virbr0 started
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,559::context::144::root::(register_async) Async
action: Retrieve applied config: tun vnet0 started
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,562::context::153::root::(finish_async) Async
action: Retrieve applied config: ethernet ens3 finished
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,562::context::153::root::(finish_async) Async
action: Retrieve applied config: bridge virbr0 finished
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,562::context::153::root::(finish_async) Async
action: Retrieve applied config: tun vnet0 finished
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,585::ifaces::668::root::(_remove_unknown_type_interfaces)
Interface lo is type unknown and will be ignored during the
activation
MainProcess|jsonrpc/3::DEBUG::2021-02-09
15:04:19,585::ifaces::668::root::(_remove_unknown_type_interfaces)
Interface virbr0-nic is type unknown and will be ignored
during the activation
--
     res = func(*args, **kwargs)
   File
"/usr/lib/python3.6/site-packages/vdsm/network/api.py", line
206, in setupNetworks
     _setup_networks(networks, bondings, options)
   File
"/usr/lib/python3.6/site-packages/vdsm/network/api.py", line
230, in _setup_networks
     netswitch.configurator.setup(networks, bondings,
options, in_rollback)
   File
"/usr/lib/python3.6/site-packages/vdsm/network/netswitch/configurator.py",
line 71, in setup
     _setup_nmstate(networks, bondings, options, in_rollback)
   File
"/usr/lib/python3.6/site-packages/vdsm/network/netswitch/configurator.py",
line 94, in _setup_nmstate
     nmstate.setup(desired_state, verify_change=not in_rollback)
   File
"/usr/lib/python3.6/site-packages/vdsm/network/nmstate/api.py",
line 50, in setup
     state_apply(desired_state, verify_change=verify_change)
   File
"/usr/lib/python3.6/site-packages/libnmstate/netapplier.py",
line 69, in apply
     net_state = NetState(desired_state, current_state,
save_to_disk)
   File
"/usr/lib/python3.6/site-packages/libnmstate/net_state.py",
line 64, in __init__
     self._ifaces.gen_route_rule_metadata(self._route_rule,
self._route)
   File
"/usr/lib/python3.6/site-packages/libnmstate/ifaces/ifaces.py",
line 617, in gen_route_rule_metadata
     route_state, self._kernel_ifaces
   File
"/usr/lib/python3.6/site-packages/libnmstate/route_rule.py",
line 197, in gen_metadata
     route_state, route_table, ifaces
   File
"/usr/lib/python3.6/site-packages/libnmstate/route_rule.py",
line 233, in _iface_for_route_table
     "Failed to find interface to with route table ID "

> CentOS stream on it's own had some issues and I am not
> sure if anyone tried to successfully
> deploy the host there.
>
I do not get it - I hope you don't mind my saying - since
Redhat's announcement to all of us a while ago, about now
Centos Stream being the only way into the future, I hear
that... well, not really.... Not true? Which one is it?

>
> Regards,
> Ales
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA <https://www.redhat.com>
>
> amusil@redhat.com <mailto:amusil@redhat.com> IM: amusil
>
> <https://red.ht/sig>
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VKODYI25VXM6RDGFYLNCZLSSBAYONOTQ/