-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
?
-
?
-
?
-
?
-
None
-
-
-
Critical
We cannot reach the non dpdk mgmt nets via floating IP.
To reproduce the problem:
openstack network create --external --share --provider-physical-network access --provider-network-type vlan --provider-segment $ACCESS_VLAN access openstack subnet create --subnet-range $ACCESS_VLAN_SUBNET --allocation-pool start=$ACCESS_VLAN_SUBNET_START,end=$ACCESS_VLAN_SUBNET_END --gateway $ACCESS_VLAN_SUBNET_GW --no-dhcp --network access access openstack router create router openstack router set router --external-gateway access openstack network create --provider-network-type vlan --provider-physical-network dpdkdata0 --disable-port-security dpdk-data1 openstack subnet create --gateway 10.10.20.254 --network dpdk-data1 --subnet-range 10.10.20.0/24 --allocation-pool start=10.10.20.100,end=10.10.20.200 dpdk-data1_subnet openstack router add subnet router dpdk-data1_subnet
For example having this VMs created:
sh-5.1$ openstack server list --all --long +--------------------------------------+-----------+--------+------------+-------------+----------------------------------------+---------------------------------------+--------------------------------------+--------------------+-------------------+--------------------------------+------------+-------------+ | ID | Name | Status | Task State | Power State | Networks | Image Name | Image ID | Flavor | Availability Zone | Host | Properties | Host Status | +--------------------------------------+-----------+--------+------------+-------------+----------------------------------------+---------------------------------------+--------------------------------------+--------------------+-------------------+--------------------------------+------------+-------------+ | 6798ff57-2e74-456d-a9a7-b0951af90c83 | instance2 | ACTIVE | None | Running | dpdk-data1=10.10.20.104 | rhel-guest-image-8.4-1245-nfv3.x86_64 | bafba973-5506-4125-8c4f-4ad62abb1959 | nfv_qe_base_flavor | nova | compute-1.ctlplane.example.com | | UP | | 07496f5c-e6a3-4d7d-bf68-7101a48e693d | instance1 | ACTIVE | None | Running | dpdk-data1=10.10.20.118, 10.46.X.X | rhel-guest-image-8.4-1245-nfv3.x86_64 | bafba973-5506-4125-8c4f-4ad62abb1959 | nfv_qe_base_flavor | nova | compute-0.ctlplane.example.com | | UP | +--------------------------------------+-----------+--------+------------+-------------+----------------------------------------+---------------------------------------+--------------------------------------+--------------------+-------------------+--------------------------------+------------+-------------+
We don't have ping/ssh to VM:
[zuul@tigon25 ~]$ ssh -oconnecttimeout=30 10.46.X.X ssh: connect to host 10.46.X.X port 22: Connection timed out [zuul@tigon25 ~]$ ping -c1 10.46.X.X PING 10.46.X.X (10.46.X.X) 56(84) bytes of data.--- 10.46.X.X ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms[zuul@tigon25 ~]$ ssh -oconnecttimeout=30 10.46.X.X ssh: connect to host 10.46.X.X port 22: Connection timed out [zuul@tigon25 ~]$ ping -c1 10.46.X.X PING 10.46.X.X (10.46.X.X) 56(84) bytes of data.--- 10.46.X.X ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms
NAD seems to be fine:
[zuul@controller-0 ~]$ oc get network-attachment-definitions.k8s.cni.cncf.io dpdkdata0 -oyaml
apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"k8s.cni.cncf.io/v1","kind":"NetworkAttachmentDefinition","metadata":{"annotations":{},"labels":{"osp/net":"dpdkdata0"},"name":"dpdkdata0","namespace":"openstack"},"spec":{"config":"{\n \"cniVersion\": \"0.3.1\",\n \"name\": \"dpdkdata0\",\n \"type\": \"bridge\",\n \"bridge\": \"ospbr\",\n \"ipam\": {}\n}\n"}}
creationTimestamp: "2024-08-09T10:06:40Z"
generation: 1
labels:
osp/net: dpdkdata0
name: dpdkdata0
namespace: openstack
resourceVersion: "76800"
uid: d09f9990-8cd2-4e2c-b171-9094cd3f87bb
spec:
config: |
{
"cniVersion": "0.3.1",
"name": "dpdkdata0",
"type": "bridge",
"bridge": "ospbr",
"ipam": {}
}
If we attach the FIP to the dpdkmgmt net we have connectivity.