[ovirt-users] Re: Unable to install on a bonded NIC
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
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/2ZDHQ4BIZZKZIJNZNMVLQCONFAIJO3J3/
[ovirt-users] Re: Unable to install on a bonded NIC
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_using_the_command_line/index.html#Installing_Red_Hat_Enterprise_Linux_Hosts_SHE_deployment_host > > 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-le...@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/C7C2UAKG2I7FHW4KEWW4KMBASUDJ2PDM/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/Z6JNT7SFDQG4OYU4EAAVXTZMFQY7CFE2/
[ovirt-users] Re: Unable to install on a bonded NIC
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.cec...@gmail.com> wrote:
>
>
> On Tue, Feb 8, 2022 at 10:41 PM Tim W. via Users 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/html/administration_guide/sect-network_bonding#Bonding_Modes
>
> Actually here below in hosted engine installation guide:
>
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_command_line/installing_hosts_for_rhv_she_cli_deploy#Recommended_practices_for_configuring_host_networks_SHE_cli_deploy
>
> 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-le...@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/M5URESC32W4MQ2HVB2HMSXAKCSCQTKFX/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/PFDZYHKKNOAFD7WLLIOFD4D5TYBE2O3C/
[ovirt-users] Re: Unable to install on a bonded NIC
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
wrote:
On Tue, Feb 8, 2022 at 10:41 PM Tim W. via Users 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/html/administration_guide/sect-network_bonding#Bonding_Modes
Actually here below in hosted engine installation guide:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_command_line/installing_hosts_for_rhv_she_cli_deploy#Recommended_practices_for_configuring_host_networks_SHE_cli_deploy
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-le...@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/M5URESC32W4MQ2HVB2HMSXAKCSCQTKFX/
[ovirt-users] Re: Unable to install on a bonded NIC
On Tue, Feb 8, 2022 at 10:41 PM Tim W. via Users 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/html/administration_guide/sect-network_bonding#Bonding_Modes
Actually here below in hosted engine installation guide:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_command_line/installing_hosts_for_rhv_she_cli_deploy#Recommended_practices_for_configuring_host_networks_SHE_cli_deploy
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-le...@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/SG227ZIDUQR2CBTZ4UKAKJYMFSODHXDU/
[ovirt-users] Re: Unable to install on a bonded NIC
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:
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
wrote:
What is your bond name ?
On Tue, Feb 8, 2022 at 23:41, Tim W. via Users 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-le...@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/6AYCPB63G6INUDEFIQP2KI6SU2UFS6XF/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/E6ETDK6FM5BVUS32RJG2IAP6DWUVCC74/
[ovirt-users] Re: Unable to install on a bonded NIC
What is your bond name ?
On Tue, Feb 8, 2022 at 23:41, Tim W. via Users 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-le...@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/6AYCPB63G6INUDEFIQP2KI6SU2UFS6XF/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/DCQTL2PEIIMKPKZFNSPYUNMPK2SJBUL2/
[ovirt-users] Re: Unable to install on a bonded NIC
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-le...@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/6AYCPB63G6INUDEFIQP2KI6SU2UFS6XF/
[ovirt-users] Re: Unable to install on a bonded NIC
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 ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/O7VW3MDA3PWDF7BEZHQAXFO5EEOMU7IO/
[ovirt-users] Re: Unable to install on a bonded NIC
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 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-le...@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/72G4Y5WXPKFRM24JQS7AV3CCPZDEQBBH/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/FIM3VRZMKLOYYSSCH2QSFTUQSBSRKM4J/
[ovirt-users] Re: Unable to install on a bonded NIC
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-le...@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/72G4Y5WXPKFRM24JQS7AV3CCPZDEQBBH/
