Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1482180 - TestOnly: TC act_vlan: allow setting VLAN priority
TestOnly: TC act_vlan: allow setting VLAN priority
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iproute (Show other bugs)
7.5
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Phil Sutter
Jaroslav Aster
: TestOnly
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-16 11:54 EDT by Simon Horman
Modified: 2018-04-10 10:31 EDT (History)
3 users (show)

See Also:
Fixed In Version: iproute-4.11.0-4.el7
Doc Type: Enhancement
Doc Text:
Feature: tc vlan action now allows setting VLAN priority value. Reason: tc vlan action was incomplete regarding modification of priority field in VLAN header. Result: VLAN packets' priority value may be correctly adjusted using tc vlan action.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 10:31:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0815 None None None 2018-04-10 10:31 EDT

  None (edit)
Description Simon Horman 2017-08-16 11:54:44 EDT
Preface:

The intention of this bug is to provide insight into a feature proposed by Netronome for inclusion in RHEL 7.5.

Description:

act_vlan allows modification of VLAN. This has been enhanced to allow setting of the VLAN priority.

Status:

Upstream since v4.9.0

0e43ed9deae8 ("tc: m_vlan: Add priority option to push vlan action")
Comment 5 errata-xmlrpc 2018-04-10 10:31:17 EDT
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/RHEA-2018:0815

Note You need to log in before you can comment on or make changes to this bug.