+++ This bug was initially created as a clone of Bug #2026876 +++ Description of problem: vlan filtering is failed while applying on veth ports. We don't use them error reconciling NodeNetworkConfigurationPolicy at desired state apply: failed to enable vlan-filtering via nmcli: , failed to enable vlan filtering via nmcli: failed to execute nmcli con mod veth0817ddf6 bridge-port.vlans 2-4094: 'exit status 10', '', 'Error: unknown connection 'veth0817ddf6'. Version-Release number of selected component (if applicable): 4.x How reproducible: always Steps to Reproduce: 1. Apply any nncp yaml with vlan-filtering fields. Sample given in additional info. 2. 3. Actual results: nncp failed to create Expected results: NNCP creation should be successful. Additional info: Use below yaml for configuring and reproducing: apiVersion: nmstate.io/v1beta1 kind: NodeNetworkConfigurationPolicy metadata: name: upgrade-br-marker spec: desiredState: interfaces: - bridge: options: stp: enabled: false port: [] ipv4: dhcp: false enabled: false ipv6: enabled: false name: upg-br-mark state: up type: linux-bridge nodeSelector: kubernetes.io/hostname: cnv-qe-infra-32.cnvqe2.lab.eng.rdu2.redhat.com
Verified by following the same scenario as in the bug description. CNV Version: 4.8.3 nmstate-handler: v4.8.3-8
Just to clarify - in addition to the original scenario, I also verified that the bridge interface was successfully deleted, after applying "state: absent" (instead of "state: up") in the NNCP.
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 (Moderate: OpenShift Virtualization 4.8.3 Images security and bug fix update), 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/RHSA-2021:4914