-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
None
-
None
-
1
-
False
-
-
False
-
?
-
None
-
Deploy
-
-
-
-
VANS-021
-
1
-
Moderate
The octavia net-attach-def doc example has an incorrect value for the route "dst" and will cause the ovn-controller-ovs pods to fail.
Doc: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/deploying_red_hat_openstack_services_on_openshift/index#proc_attaching-service-pods-to-the-isolated-networks_preparing_networks
Current example:
---
apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
labels:
osp/net: octavia
name: octavia
namespace: openstack
spec:
config: |
{
"cniVersion": "0.3.1",
"name": "octavia",
"type": "bridge",
"bridge": "octbr",
"ipam": {
"type": "whereabouts",
"range": "192.0.2.0/16",
"range_start": "192.0.2.30",
"range_end": "192.0.2.70",
"routes": [
{
"dst": "192.1.2.0/16", #<<<<<ISSUE HERE
"gw" : "192.0.2.150"
}
]
}
}
---
Should be:
---
apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
labels:
osp/net: octavia
name: octavia
namespace: openstack
spec:
config: |
{
"cniVersion": "0.3.1",
"name": "octavia",
"type": "bridge",
"bridge": "octbr",
"ipam": {
"type": "whereabouts",
"range": "192.0.0.0/16", #<<<FIX THIS TOO
"range_start": "192.0.2.30",
"range_end": "192.0.2.70",
"routes": [
{
"dst": "192.1.0.0/16", #<<<<CORRECTED
"gw" : "192.0.2.150"
}
]
}
}
---
See this KCS for more details on the failure caused by this: https://access.redhat.com/solutions/7129413
- duplicates
-
OSPRH-18037 Octavia management CIDR is not consistent in the documentation
-
- Closed
-