Tacked by bug 1771969 the procedure to defining static routes on hosts in RHV-4.4 is documented. This bug tracks the verification, that defining static routes is working like documented.
Please note that the new procedure will work only if NetworkManager manges the related interfaces.
This bug is in modified state and targeted to 4.4.1. Can we re-target to 4.4.0 and move to QE?
(In reply to Sandro Bonazzola from comment #2)
> This bug is in modified state and targeted to 4.4.1. Can we re-target to
> 4.4.0 and move to QE?
Nmstate-0.2.6-6.el8.noarch + pathch https://gerrit.ovirt.org/#/c/108336/2/lib/vdsm/network/netswitch/configurator.py
OS: RHEL 8.2
It is recommended to document that the custom static-route will be kept whenever
the related route interface/bond exists and has an IP address. And will be removed if not.
As a result, there is different behavior between VM-Network and Non-VM-Network.
A VM-Network is based on a bridge, while Non-VM-Network on an interface.
So replacing interface/bond (by moving the Network to other interfaces/bond)
will not affect the route that related to VM-Network but will delete a route that related to a Non-VM-Network
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (RHV RHEL Host (ovirt-host) 4.4), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.