Description of problem: Today the OCP 4.4 UI with CNV offers to create VM vNICS with a SLIRP binding, this must not be permited in downstream, as in downstream we do not have slirp support (it's technically not there). Version-Release number of selected component (if applicable): CNV 2.3 How reproducible: Always Steps to Reproduce: 1. Create a VM 2. Select to add an additional vNIC, see SLRIP option in the list of bindings 3. Actual results: Expected results: Additional info:
Moving to high, as a VM cerated with that binding will not boot iiuic
This is bad Moving to OCP under console kubevirt plugin
@Andrew I think we will need to document this issue - to recommend users not to use SLIRP
ok, cloning for 4.4.z
@Nelly Release note PR is ready for review: https://github.com/openshift/openshift-docs/pull/21615
verified on 4.5.0-0.nightly-2020-05-12-065413.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409