[ovirt-users] Fibre Channel storage issue
Thanks everyone for helping me through the last issue I had. Once I changed
bonding mode to 2, everything worked.
However, now I have another issue.
I'm trying to install this using fibre channel storage. I set up a new lun
from my storage array, assigned it to my host, and configured multipathing.
All looks good. Then, when I ran the install script, I got the following error:
[ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is
"[Physical device initialization failed. Please check that the device is empty
and accessible by the host.]". HTTP response code is 400.[ ERROR ] fatal:
[localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation
Failed\". Fault detail is \"[Physical device initialization failed. Please
check that the device is empty and accessible by the host.]\". HTTP response
code is 400."}
Google says that's because the lun is dirty - maybe reused. I tried doing the
suggested - I used dd to write all zeroes to the lun. I used wipefs on the
lun. I deleted the lun from the array and created a new one. No matter what I
did with that lun, it's still showing up with this error.
I then created a second LUN. I mapped it to the host, and attempted to use
that lun for storage - and it worked!
There must be a dirty config somewhere on this thing that I need to clean up
from that first lun.
Anybody know what I might have to clean up on this host to clear out that old
config?___
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/CTFW546WOEVCDZ4C7EZMDLROQ7IKUOU6/
[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
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/
