Thew new way of defining static routes proposed in https://bugzilla.redhat.com/show_bug.cgi?id=1311590#c20 should be added to the documentation. The official documentation will supersede https://access.redhat.com/solutions/46060 for RHV-4.4
The following topics explain how to add or remove static routes: - https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4-beta/html/administration_guide/chap-logical_networks#proc-Adding-a-static-route-on-a-host - https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4-beta/html/administration_guide/chap-logical_networks#proc-Removing-a-static-route-on-a-host The following nmstate topic mentions static routes: - https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4-beta/html-single/administration_guide/index#con-Network-Manager-Stateful-Configuration-nmstate
Hi Rolfe In the Add section at https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4-beta/html-single/administration_guide/index#proc-Adding-a-static-route-on-a-host 9.1.6. Adding a static route on a host At the example below "metric: 100" can be removed, it not must: routes: config: - destination: 192.168.123.0/24 metric: 100 <- should be removed from the example because it not required, if not entered it will get a default value from the system. next-hop-address: 192.168.178.1 next-hop-interface: eth1 In the delete section: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4-beta/html-single/administration_guide/index#proc-Removing-a-static-route-on-a-host At the example below: "[eth1]" should be changed to: "[{“name”: eth1}]" routes: config: - destination: 192.168.123.0/24 metric: 100 next-hop-address: 192.168.178. next-hop-interface: eth1 state: absent interfaces: [eth1] <- should be changed to: [{“name”: eth1}] Thx Roni
Also this from https://bugzilla.redhat.com/show_bug.cgi?id=1771977#c5 "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"
Thanks Roni. I've made the changes you suggested. Please review the changes here: https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Virtualization/-/merge_requests/1720 If it looks good, just comment "LGTM" below.
LGTM Thanks for fixing it
Merged and published.