Bug 2026881

Summary:	[4.8.3] vlan-filtering is getting applied on veth ports
Product:	Container Native Virtualization (CNV)	Reporter:	Petr Horáček <phoracek>
Component:	Networking	Assignee:	Radim Hrazdil <rhrazdil>
Status:	CLOSED ERRATA	QA Contact:	Meni Yakove <myakove>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.8.3	CC:	cnv-qe-bugs, gkapoor, myakove, phoracek, rhrazdil, ysegev
Target Milestone:	---
Target Release:	4.8.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kubernetes-nmstate-handler-container-v4.8.3-8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2026876	Environment:
Last Closed:	2021-12-02 17:01:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2026876
Bug Blocks:

Description Petr Horáček 2021-11-26 10:47:30 UTC

+++ 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

Comment 1 Yossi Segev 2021-11-29 11:42:04 UTC

Verified by following the same scenario as in the bug description.
CNV Version: 4.8.3
nmstate-handler: v4.8.3-8

Comment 2 Yossi Segev 2021-11-29 16:29:45 UTC

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.

Comment 6 errata-xmlrpc 2021-12-02 17:01:42 UTC

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