-
Bug
-
Resolution: Done-Errata
-
Major
-
CNV v4.14.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
Important
-
No
Description of problem:
VM cannot be started after adding 2nd nic, it seems it has some issues in VM spec while creating it from UI, the VM could be started after made changes like below.
1. interfaces:
- macAddress: '02:bc:ea:00:00:0c'
masquerade: {}
model: virtio
name: default
- macAddress: '02:bc:ea:00:00:0d'
model: virtio
name: nic-pure-termite
Change it like below:
interfaces:
- macAddress: '02:bc:ea:00:00:0c'
masquerade: {}
model: virtio
name: default
- macAddress: '02:bc:ea:00:00:0d'
model: virtio
name: nic-pure-termite
bridge: {}
2. networks:
- name: default
pod: {}
- multus:
networkName: test-ns/bridge-network
name: nic-pure-termite
need to change it to:
networks:
- name: default
pod: {}
- multus:
networkName: bridge-network
name: nic-pure-termite
Version-Release number of selected component (if applicable):
4.14.0
How reproducible:
100%
Steps to Reproduce:
1. configure nncp with dhcp 2. create nad with bridge 3. create vm with the nad
Actual results:
VM is not started
Expected results:
VM is started
Additional info:
- links to
-
RHSA-2023:113931
OpenShift Virtualization 4.14.0 Images
- mentioned on