So I'm running a fresh install of oVirt on a new Centos Stream node. Fresh install. I installed the OS with bonded interfaces. I bonded them during the install via anaconda. I followed the doc here: https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_usi... When I got to the hosted-engine --deploy step, it errored out saying, "Only Team devices are present. Teaming is unsupported." However, I'm not teaming my network adapters at all. I'm bonding them: [root@mustafar ~]# cat /etc/sysconfig/network-scripts/ifcfg-Bond_connection_1 BONDING_OPTS="mode=balance-rr downdelay=0 miimon=1 updelay=0" TYPE=Bond BONDING_MASTER=yes PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME="Bond connection 1" UUID=[redacted] DEVICE=bond0 ONBOOT=yes IPADDR=192.168.5.83 PREFIX=24 GATEWAY=192.168.5.1 DNS1=192.168.5.2 DNS2=192.168.5.3 DNS3=192.168.5.4 DOMAIN=[redacted] [root@mustafar ~]# What gives with this?
From the install script output: ... [ INFO ] Checking available network interfaces: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Detecting interface on existing management bridge] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set variable for supported bond modes] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get all active network interfaces] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Filter bonds with bad naming] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Generate output list] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Collect interface types] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check for Team devices] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get list of Team devices] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Collect Team devices] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Filter team devices] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if only team devices are available] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Only Team devices are present. Teaming is unsupported."} [ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook [ INFO ] Stage: Clean up ...
Can you execute the commands from /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/filter_team_devices.yml (on the Hypervisor) and share the output ? The first task executes 'nmcli -g GENERAL.TYPE device show' shows all available devices Best Regards,Strahil Nikolov On Tue, Feb 8, 2022 at 17:33, weeglos--- via Users<users@ovirt.org> wrote: From the install script output: ... [ INFO ] Checking available network interfaces: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Detecting interface on existing management bridge] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set variable for supported bond modes] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get all active network interfaces] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Filter bonds with bad naming] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Generate output list] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Collect interface types] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check for Team devices] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get list of Team devices] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Collect Team devices] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Filter team devices] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if only team devices are available] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Only Team devices are present. Teaming is unsupported."} [ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook [ INFO ] Stage: Clean up ... _______________________________________________ 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/72G4Y5WXPKFRM2...
Thanks for your reply! The only shell command in that script is the one you mentioned. Here is the output: [root@mustafar ~]# set -euo pipefail && nmcli -g GENERAL.TYPE device show bond ethernet ethernet ethernet ethernet loopback
I think I found the problem. The regex in 001_validate_network_interfaces.yml really wants there to be a number after the 'bond' identifier, i.e. bond0. However, the regex is as follows: bond_valid_name="{{ iface_item | regex_search('(^bond[0-9]+)') }}" which will not return a good value if just 'bond' is passed to it (the output of nmcli -g GENERAL.TYPE device show). However, I am not an ansible expert, nor am I an expert on how these scripts are called. I humbly request someone else's expert opinion on this. Thanks again.
What is your bond name ? On Tue, Feb 8, 2022 at 23:41, Tim W. via Users<users@ovirt.org> wrote: I think I found the problem. The regex in 001_validate_network_interfaces.yml really wants there to be a number after the 'bond' identifier, i.e. bond0. However, the regex is as follows: bond_valid_name="{{ iface_item | regex_search('(^bond[0-9]+)') }}" which will not return a good value if just 'bond' is passed to it (the output of nmcli -g GENERAL.TYPE device show). However, I am not an ansible expert, nor am I an expert on how these scripts are called. I humbly request someone else's expert opinion on this. Thanks again. _______________________________________________ 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/6AYCPB63G6INUD...
bond0 is the name of the bond. However, the output of the query to network manager that is coming up is just 'bond' [root@mustafar ~]# ip addr sho bond06: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether [redacted] brd ff:ff:ff:ff:ff:ff inet 192.168.5.83/24 brd 192.168.5.255 scope global noprefixroute bond0 valid_lft forever preferred_lft forever inet6 [redacted]/64 scope global dynamic noprefixroute valid_lft 29sec preferred_lft 19sec inet6 fe80::7766:8381:983a:9198/64 scope link noprefixroute valid_lft forever preferred_lft forever On Tuesday, February 8, 2022, 05:06:58 PM CST, Strahil Nikolov <hunter86_bg@yahoo.com> wrote: What is your bond name ? On Tue, Feb 8, 2022 at 23:41, Tim W. via Users<users@ovirt.org> wrote: I think I found the problem. The regex in 001_validate_network_interfaces.yml really wants there to be a number after the 'bond' identifier, i.e. bond0. However, the regex is as follows: bond_valid_name="{{ iface_item | regex_search('(^bond[0-9]+)') }}" which will not return a good value if just 'bond' is passed to it (the output of nmcli -g GENERAL.TYPE device show). However, I am not an ansible expert, nor am I an expert on how these scripts are called. I humbly request someone else's expert opinion on this. Thanks again. _______________________________________________ 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/6AYCPB63G6INUD...
On Tue, Feb 8, 2022 at 10:41 PM Tim W. via Users <users@ovirt.org> wrote:
I think I found the problem. The regex in 001_validate_network_interfaces.yml really wants there to be a number after the 'bond' identifier, i.e. bond0. However, the regex is as follows:
bond_valid_name="{{ iface_item | regex_search('(^bond[0-9]+)') }}"
which will not return a good value if just 'bond' is passed to it (the output of nmcli -g GENERAL.TYPE device show).
However, I am not an ansible expert, nor am I an expert on how these scripts are called. I humbly request someone else's expert opinion on this.
Thanks again.
I think the main failure reason is about the current bonding mode: balance-rr that is not supported: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/htm... Actually here below in hosted engine installation guide: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/htm... is stated: " If the ovirtmgmt network is not used by virtual machines, the network may use any supported bonding mode. " But in 001_validate_network_interfaces.yml there is: - name: Set variable for supported bond modes set_fact: acceptable_bond_modes: ['active-backup', 'balance-xor', 'broadcast', '802.3ad'] and then a when condition with hostvars[inventory_hostname]['ansible_' + iface_item]['mode'] in acceptable_bond_modes so that the balance-rr interface is filtered out. Not digged about the "false" positive regarding messages about only team devices detected... HIH, Gianluca
That did it! I changed bonding mode from 0 to 2 (XOR) and it installs! I think that error message needs to be a bit more descriptive, and documentation should be updated to reflect that bonding mode 0 is not supported. Thanks all for your help! On Tuesday, February 8, 2022, 05:19:58 PM CST, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote: On Tue, Feb 8, 2022 at 10:41 PM Tim W. via Users <users@ovirt.org> wrote: I think I found the problem. The regex in 001_validate_network_interfaces.yml really wants there to be a number after the 'bond' identifier, i.e. bond0. However, the regex is as follows: bond_valid_name="{{ iface_item | regex_search('(^bond[0-9]+)') }}" which will not return a good value if just 'bond' is passed to it (the output of nmcli -g GENERAL.TYPE device show). However, I am not an ansible expert, nor am I an expert on how these scripts are called. I humbly request someone else's expert opinion on this. Thanks again. I think the main failure reason is about the current bonding mode: balance-rr that is not supported: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/htm... Actually here below in hosted engine installation guide: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/htm... is stated: "If the ovirtmgmt network is not used by virtual machines, the network may use any supported bonding mode." But in 001_validate_network_interfaces.yml there is: - name: Set variable for supported bond modes set_fact: acceptable_bond_modes: ['active-backup', 'balance-xor', 'broadcast', '802.3ad'] and then a when condition with hostvars[inventory_hostname]['ansible_' + iface_item]['mode'] in acceptable_bond_modes so that the balance-rr interface is filtered out.Not digged about the "false" positive regarding messages about only team devices detected... HIH, Gianluca
An alternative, you install it without bonding, you install the manager on eth0, you install the HE and you add the host and there you create the bonding and the corresponding vlans of each host El mié., 9 de febrero de 2022 12:40 p. m., Timothy J. Wielgos via Users < users@ovirt.org> escribió:
That did it!
I changed bonding mode from 0 to 2 (XOR) and it installs!
I think that error message needs to be a bit more descriptive, and documentation should be updated to reflect that bonding mode 0 is not supported.
Thanks all for your help!
On Tuesday, February 8, 2022, 05:19:58 PM CST, Gianluca Cecchi < gianluca.cecchi@gmail.com> wrote:
On Tue, Feb 8, 2022 at 10:41 PM Tim W. via Users <users@ovirt.org> wrote:
I think I found the problem. The regex in 001_validate_network_interfaces.yml really wants there to be a number after the 'bond' identifier, i.e. bond0. However, the regex is as follows:
bond_valid_name="{{ iface_item | regex_search('(^bond[0-9]+)') }}"
which will not return a good value if just 'bond' is passed to it (the output of nmcli -g GENERAL.TYPE device show).
However, I am not an ansible expert, nor am I an expert on how these scripts are called. I humbly request someone else's expert opinion on this.
Thanks again.
I think the main failure reason is about the current bonding mode: balance-rr that is not supported:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/htm...
Actually here below in hosted engine installation guide:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/htm...
is stated: " If the ovirtmgmt network is not used by virtual machines, the network may use any supported bonding mode. "
But in 001_validate_network_interfaces.yml there is:
- name: Set variable for supported bond modes set_fact: acceptable_bond_modes: ['active-backup', 'balance-xor', 'broadcast', '802.3ad']
and then a when condition with
hostvars[inventory_hostname]['ansible_' + iface_item]['mode'] in acceptable_bond_modes
so that the balance-rr interface is filtered out. Not digged about the "false" positive regarding messages about only team devices detected...
HIH, Gianluca
_______________________________________________ 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/M5URESC32W4MQ2...
An alternative, you install it without bonding, you install the manager on eth0, you install the HE and you add the host and there you create the bonding and the corresponding vlans of each host El mar., 8 de febrero de 2022 3:00 a. m., weeglos--- via Users < users@ovirt.org> escribió:
So I'm running a fresh install of oVirt on a new Centos Stream node. Fresh install.
I installed the OS with bonded interfaces. I bonded them during the install via anaconda.
I followed the doc here: https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_usi...
When I got to the hosted-engine --deploy step, it errored out saying, "Only Team devices are present. Teaming is unsupported."
However, I'm not teaming my network adapters at all. I'm bonding them:
[root@mustafar ~]# cat /etc/sysconfig/network-scripts/ifcfg-Bond_connection_1 BONDING_OPTS="mode=balance-rr downdelay=0 miimon=1 updelay=0" TYPE=Bond BONDING_MASTER=yes PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME="Bond connection 1" UUID=[redacted] DEVICE=bond0 ONBOOT=yes IPADDR=192.168.5.83 PREFIX=24 GATEWAY=192.168.5.1 DNS1=192.168.5.2 DNS2=192.168.5.3 DNS3=192.168.5.4 DOMAIN=[redacted] [root@mustafar ~]#
What gives with this? _______________________________________________ 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/C7C2UAKG2I7FHW...
Hi, I'm in the exact same situation. I got the error: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Only Team devices are present. Teaming is unsupported."} [ ERROR ] Failed to execute stage 'Environment customization': Failed executing ansible-playbook while my configuration is: bond0 d0b22e4d-8003-43b6-8090-4ad32ed0fc70 bond ntw Where bond0 is configured with "mode=balance-xor" . Any suggestion on where I can find the problem? I've already done all the checks here (excluding the installation without bonging) but i'm not able to come to a solution Any help will be appreciated
participants (8)
-
gaetano.sasanelli＠gmail.com -
Gianluca Cecchi -
Ingeniero especialista Redhat / Suse -
jaime luque -
Strahil Nikolov -
Tim W. -
Timothy J. Wielgos
-
weeglos＠yahoo.com