[ovirt-users] Re: Unable to install on a bonded NIC
On Tue, Feb 8, 2022 at 10:41 PM Tim W. via Users <users(a)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/...
Actually here below in hosted engine installation guide:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/...
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
Attachments:
- attachment.html (text/html — 2.9 KB)