-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
Getting 'Device profile not found error' in EDPM deployment for OvS DPDK using os-net-config network configs with nmstate provider.
[2024-02-01T07:00:18Z INFO nmstate::query_apply::net_state] Rollbacked to checkpoint /org/freedesktop/NetworkManager/Checkpoint/12
NmstateError: Bug: Manager(UnknownDevice): No suitable device found for this connection (device ens2f0np0 not available because profile is not compatible with device (mismatching interface name)).
os-net-config network configs used:
ansibleVars:
edpm_network_config_nmstate: true
edpm_network_config_template: |
—
network_config:
- type: interface
name: eno1
use_dhcp: false
default: false
- type: interface
name: eno2
use_dhcp: false
dns_servers: ["192.168.122.80"]
domain: []
addresses:
- ip_netmask: 192.168.122.100/24
routes:
- ip_netmask: 169.254.169.254/32
next_hop: 192.168.122.1
- default: true
next_hop: 192.168.122.1
- type: vlan
device: eno2
vlan_id: 202
addresses:
- ip_netmask: 172.17.0.100/24
- type: vlan
device: eno2
vlan_id: 203
addresses:
- ip_netmask: 172.18.0.100/24
- type: ovs_user_bridge
name: br-link1
use_dhcp: false
ovs_extra: "set port br-link1 tag=204"
addresses:
- ip_netmask: 172.19.0.100/24
mtu: 9000
members:
- type: ovs_dpdk_port
name: dpdk1
members:
- type: interface
name: eno3
- type: ovs_user_bridge
name: br-link2
use_dhcp: false
mtu: 9000
members:
- type: ovs_dpdk_port
name: dpdk2
members:
- type: interface
name: eno4
- relates to
-
OSPRH-4276 End-to-end OSP host network provision with new nmstate backend
- Review
- links to
-
RHBA-2024:133297 Release of components for Red Hat OpenStack Services on OpenShift 18.0