RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2058292 - [RFE] Allow configuration of VLAN on an unmanaged interface
Summary: [RFE] Allow configuration of VLAN on an unmanaged interface
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nmstate
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 9.2
Assignee: Gris Ge
QA Contact: Mingyu Shi
Mayur Patil
URL:
Whiteboard:
Depends On:
Blocks: 2110307
TreeView+ depends on / blocked
 
Reported: 2022-02-24 16:26 UTC by Petr Horáček
Modified: 2023-05-14 13:23 UTC (History)
12 users (show)

Fixed In Version: nmstate-2.2.1-1.el9
Doc Type: Enhancement
Doc Text:
.NetworkManager now allows VLAN configuration over unmanaged interface With this enhancement, you can use an unmanaged networking interface as a base interface when configuring virtual LAN (VLAN) with NetworkManager. As a result, the VLAN base interface remains intact unless changed explicitly through the `nmcli device set _enp1s0_ managed true` command or other API of NetworkManager.
Clone Of:
: 2110307 (view as bug list)
Environment:
Last Closed: 2023-05-09 07:30:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-125 0 None None None 2023-01-22 15:28:55 UTC
Red Hat Issue Tracker RHELPLAN-113697 0 None None None 2022-02-24 16:36:09 UTC
Red Hat Product Errata RHBA-2023:2190 0 None None None 2023-05-09 07:31:13 UTC

Description Petr Horáček 2022-02-24 16:26:01 UTC 
Description of problem:

It is not possible to configure a VLAN interface on unmanaged NIC. That forces
users who only want to create a VLAN inteface to take ownership over possibly
shared underlying NIC.


Version-Release number of selected component (if applicable):
RHEL 8.4


How reproducible:
Always


Steps to Reproduce:
1. Have a node with unmanaged NIC eno5np0
2. Apply the following nmstate configuration:
interfaces:
- name: eno5np0.350
  type: vlan
  state: up
  ipv4:
    enabled: true
    dhcp: true
    auto-gateway: false
  vlan:
    base-iface: "eno5np0"
    id: 350


Actual results:
type: vlan failed: error=nm-manager-error-quark: Failed to find a compatible device for this connection (3)


Expected results:
If it is something possible to do with Linux networking, it would be useful if
in this case it was possible to configure the VLAN while leaving the NIC
unmanaged (or managed by some tool that may or may not use NetworkManager).


Additional info:
This was reported and described in detail in the context of kubernetes nmstate
in https://bugzilla.redhat.com/show_bug.cgi?id=2017623#c13.
Comment 3 Gris Ge 2022-04-24 05:07:37 UTC 
Hi Petr,

Are you expecting the support of 


```yml
interfaces:
- name: eno5np0.350
  type: vlan
  state: up
  ipv4:
    enabled: true
    dhcp: true
    auto-gateway: false
  vlan:
    base-iface: "eno5np0"
    id: 350
- name: eno5np0
  type: ethernet
  state: ignore
```

Currently, NetworkManager does not allow this, technically it is doable, could you provides:

 * Why NetworkManager should not try to manage the vlan parent interface?
 * What feature/function of CNV/openshift is blocked by this?
 * When CNV/openshfit expecting the release of this feature?
Comment 4 Petr Horáček 2022-04-25 13:37:56 UTC 
Hello,

yes, this is pretty much what we'd need. Ideally without the need to mention eno5np0 (ignored) at all.

> * Why NetworkManager should not try to manage the vlan parent interface?

Because of something else manages it. In OpenShift, the SR-IOV operator is AFAIK not using NM to configure VFs etc. When it starts working with a NIC, it explicitly makes it unmanaged.

- https://github.com/k8snetworkplumbingwg/sriov-network-operator/blob/236be9826955e819e8fe56cd56cdfa62a8e87344/pkg/utils/utils.go#L375
- https://github.com/k8snetworkplumbingwg/sriov-network-operator/blob/70b25f6965a3d875cb6279f3f9ef8161ad7e0686/pkg/daemon/daemon.go#L1068


> * What feature/function of CNV/openshift is blocked by this?

Users cannot create a VLAN interface on PFs managed by the operator.

> * When CNV/openshfit expecting the release of this feature?

We already registered some complaints about it. However, I don't think this would need to be backported. So either RHEL 8.6 or 9.0?
Comment 5 Petr Horáček 2022-07-21 10:37:16 UTC 
Could we get this prioritized? Thanks!
Comment 6 Gris Ge 2022-07-22 06:51:47 UTC 
Sure. Let me ask around.
Comment 7 Gris Ge 2022-07-25 07:05:09 UTC 
According to these command, we need fixes in NM to get this supported:

ip link add test_nic1 type veth peer name test_nic1peer || true
ip link set test_nic1 up || true
ip link set test_nic1peer up || true

nmcli d set test_nic1peer managed false
nmcli d set test_nic1 managed false

nmcli c add type vlan ifname vlan1 vlan.parent test_nic1 vlan.id 100 \
    connection.autoconnect no connection.id vlan1
nmcli c up vlan1
Comment 10 Gris Ge 2022-11-17 13:40:56 UTC 
Hi Petr,

With NetworkManager-1.41.4-1.el9 , creating VLAN over unmanaged interface works well out of box in nmstate.
Comment 13 Petr Horáček 2022-11-24 11:15:28 UTC 
Oh that's awesome. Thanks so much Gris for pushing this.
Comment 14 Mingyu Shi 2023-01-30 08:07:17 UTC 
Verified with:
nmstate-2.2.5-1.el9.x86_64
nispor-1.2.9-1.el9.x86_64
NetworkManager-1.41.90-1.el9.x86_64
DISTRO=RHEL-9.2.0-20230127.12
Comment 19 errata-xmlrpc 2023-05-09 07:30:59 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 (nmstate bug fix and enhancement 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/RHBA-2023:2190
Note You need to log in before you can comment on or make changes to this bug.