Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
New directive VLAG_EGRESS_PRIORITY_MAP directive for ifcfg-* interface files introduced.
This new directive allows to change the egress priority of each network interface when it is not controlled by NetworkManager.
DescriptionFani Orestiadou
2017-03-29 11:09:19 UTC
Description of problem:
VLAN_EGRESS_PRIORITY_MAP option is not applied by modifying the ifcfg files when NetworkManager is not handling the vlan interface.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 7.3 (Maipo)
3.10.0-514.2.2.el7.x86_64
NetworkManager-1.4.0-13.el7_3.x86_64 Sun Feb 26 12:12:09 2017
How reproducible: Have the interface not handled my NetworkManager and change the egress option manually by editing the ifcfg file.
Steps to Reproduce:
1. Edit the ifcfg file with the desired priority
2. Restart network service
3. Check /proc/net/vlan/vlanX
Actual results:
The priority is not applied.
- With NM_CONTROLLED=yes
[root@localhost ~]# cat /proc/net/vlan/team0.10
team0.10 VID: 10 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 0
total bytes received 0
Broadcast/Multicast Rcvd 0
total frames transmitted 11
total bytes transmitted 1650
Device: team0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESS priority mappings:
[root@localhost ~]# vi /etc/sysconfig/network-scripts/ifcfg-team0.10
[root@localhost ~]# grep -i egress /etc/sysconfig/network-scripts/ifcfg-team0.10
VLAN_EGRESS_PRIORITY_MAP=0:3,1:3,2:3,3:3,4:3,5:3,6:3,7:3
[root@localhost ~]# systemctl restart network
[root@localhost ~]# cat /proc/net/vlan/team0.10
team0.10 VID: 10 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 0
total bytes received 0
Broadcast/Multicast Rcvd 0
total frames transmitted 10
total bytes transmitted 1308
Device: team0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESS priority mappings: 0:3 1:3 2:3 3:3 4:3 5:3 6:3 7:3 <---
- With NM_CONTROLLED=no
[root@localhost ~]# egrep -i -e "NM|egress" /etc/sysconfig/network-scripts/ifcfg-team0.10
VLAN_EGRESS_PRIORITY_MAP=0:3,1:3,2:3,3:3,4:3,5:3,6:3,7:3
NM_CONTROLLED=no
[root@localhost ~]# cat /proc/net/vlan/team0.10
team0.10 VID: 10 REORDER_HDR: 1 dev->priv_flags: 1
total frames received 0
total bytes received 0
Broadcast/Multicast Rcvd 0
total frames transmitted 22
total bytes transmitted 3161
Device: team0
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
EGRESS priority mappings: <---------
Expected results:
Have the egress priority mapping applied.
Additional info:
Customer is not able to use NetworkManager because they are using Redhat OSP for Openstack, and it is required to have it disabled.
Let me know if more info is required.
Thank you,
Fani
Hello Lukas,
Thank you for your reply. I would like to know though the reason why we don't support this. Do you mean that is not yet implemented and we can proceed with RFE or that generally will not be supported from our side?
Thank you
Hello Lukas,
The request is coming from a strategic customer and the feature is quite important for them. Is it possible to have it implemented on RHEL 7.4?
Thank you,
Fani
Comment 11David Kaspar // Dee'Kej
2017-04-11 14:09:02 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, 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-2017:2286
Description of problem: VLAN_EGRESS_PRIORITY_MAP option is not applied by modifying the ifcfg files when NetworkManager is not handling the vlan interface. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux Server release 7.3 (Maipo) 3.10.0-514.2.2.el7.x86_64 NetworkManager-1.4.0-13.el7_3.x86_64 Sun Feb 26 12:12:09 2017 How reproducible: Have the interface not handled my NetworkManager and change the egress option manually by editing the ifcfg file. Steps to Reproduce: 1. Edit the ifcfg file with the desired priority 2. Restart network service 3. Check /proc/net/vlan/vlanX Actual results: The priority is not applied. - With NM_CONTROLLED=yes [root@localhost ~]# cat /proc/net/vlan/team0.10 team0.10 VID: 10 REORDER_HDR: 1 dev->priv_flags: 1 total frames received 0 total bytes received 0 Broadcast/Multicast Rcvd 0 total frames transmitted 11 total bytes transmitted 1650 Device: team0 INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0 EGRESS priority mappings: [root@localhost ~]# vi /etc/sysconfig/network-scripts/ifcfg-team0.10 [root@localhost ~]# grep -i egress /etc/sysconfig/network-scripts/ifcfg-team0.10 VLAN_EGRESS_PRIORITY_MAP=0:3,1:3,2:3,3:3,4:3,5:3,6:3,7:3 [root@localhost ~]# systemctl restart network [root@localhost ~]# cat /proc/net/vlan/team0.10 team0.10 VID: 10 REORDER_HDR: 1 dev->priv_flags: 1 total frames received 0 total bytes received 0 Broadcast/Multicast Rcvd 0 total frames transmitted 10 total bytes transmitted 1308 Device: team0 INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0 EGRESS priority mappings: 0:3 1:3 2:3 3:3 4:3 5:3 6:3 7:3 <--- - With NM_CONTROLLED=no [root@localhost ~]# egrep -i -e "NM|egress" /etc/sysconfig/network-scripts/ifcfg-team0.10 VLAN_EGRESS_PRIORITY_MAP=0:3,1:3,2:3,3:3,4:3,5:3,6:3,7:3 NM_CONTROLLED=no [root@localhost ~]# cat /proc/net/vlan/team0.10 team0.10 VID: 10 REORDER_HDR: 1 dev->priv_flags: 1 total frames received 0 total bytes received 0 Broadcast/Multicast Rcvd 0 total frames transmitted 22 total bytes transmitted 3161 Device: team0 INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0 EGRESS priority mappings: <--------- Expected results: Have the egress priority mapping applied. Additional info: Customer is not able to use NetworkManager because they are using Redhat OSP for Openstack, and it is required to have it disabled. Let me know if more info is required. Thank you, Fani