-
Bug
-
Resolution: Unresolved
-
Critical
-
CNV v4.19.0
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
CNV v4.99.0.rhel9-2329
-
-
Critical
-
None
<Description of problem:
On VM creation trough the UI console, its impossible to add an additional interface and select a network that was create by OVN-Kuberentes's using UserDefinedNetwork or ClusterUserDefinedNetwork CRDs.
Version-Release number of selected component (if applicable):
4.19.0-0.nightly-2025-05-04-082442
How reproducible:
100%
Steps to Reproduce:
1. create OVN bridge-mapping "localnet1" $ oc apply -f - <<EOF apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: br-ex-localnet1 spec: nodeSelector: node-role.kubernetes.io/worker: '' desiredState: ovn: bridge-mappings: localnet: localnet1 bridge: br-ex state: present EOF 2. create new project $ oc new-project reproducer 3. create localnet topology using CUDN CR, selecting the project namespace name 4. $ oc apply -f - <<EOF apiVersion: k8s.ovn.org/v1 kind: ClusterUserDefinedNetwork metadata: name: localnet1 spec: namespaceSelector: matchExpressions: - key: kubernetes.io/metadata.name operator: In values: ["reproducer"] network: topology: Localnet localnet: role: Secondary physicalNetworkName: localnet1 ipam: {mode: Disabled} EOF 5. Create new VM using the wizard, and select the network created in (4) VirtualMachine > create > from template > pick any.. Customize VirtualMachine > Network Interfaces > Add network interface **The network created in (4) does not present.**
Actual results:
Its impossible to select OVN-K user defined network on the "Add network interface" modal.
Expected results:
Allow connecting VM to OVN-K user-defined network.
Additional info:
- relates to
-
CNV-52160 UI for User-defined networks: Localnet
-
- In Progress
-
-
CNV-61213 QE Automation fix/missing: On VM creation its impossilbe to select OVN-K user-defined network
-
- New
-
- links to
-
RHEA-2025:150257 OpenShift Virtualization 4.20.0 Images
- mentioned on
(2 mentioned on)