-
Bug
-
Resolution: Done
-
Undefined
-
rhos-18.0.9
-
None
-
2
-
False
-
-
False
-
?
-
rhos-dfg-networking
-
None
-
-
-
VANS-020
-
1
-
Moderate
in RHOSO 18 documentation:
The CIDR of the Octavia management network is mentioned twice:
- in the Table 3.1 Default RHOSO network https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/deploying_red_hat_openstack_services_on_openshift/assembly_preparing-rhoso-networks_preparing#ref_default-RHOSO-networks_preparing_networks
- In 3.2.2 https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/deploying_red_hat_openstack_services_on_openshift/assembly_preparing-rhoso-networks_preparing#proc_attaching-service-pods-to-the-isolated-networks_preparing_networks
In the table, the CIDR of the management network is 172.23.0.0/24
But in 3.2.2 another range is used: 192.0.2.0/16
So it's really confusing for the admins.
To ensure consistency, we should update the NetworkAttachmentDefinition with a real example from the deployment:
"type": "whereabouts", "range": "172.23.0.0/24", "range_start": "172.23.0.30", "range_end": "172.23.0.70", "routes": [ { "dst": "172.24.0.0/16", "gw" : "172.23.0.150" }
- is duplicated by
-
OSPRH-19245 [RHOSO][Docs] incorrect route "dst" example in octavia net-attach-def causes ovn-controller-ovs pods to fail
-
- Closed
-