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.
DescriptionQuique Llorente
2019-10-04 08:11:39 UTC
Description of problem:
Playing around with linux-bridges and vlan filtering functionality with iproute command 'bridge' we found that it outputs a invalid json and that's a problemn for our processing tools.
rpm version: iproute-4.18.0-11.el8.x86_64
os: Red Hat Enterprise Linux CoreOS release 4.1
[core@test-1-mfqwp-master-0 ~]$ rpm-ostree status
State: idle
AutomaticUpdates: disabled
Deployments:
* pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fb025ff2b405cf5902a451675cd27a9d702ced7c88b5a33280d42069524874c6
CustomOrigin: Managed by pivot tool
Version: 410.8.20190904.0 (2019-09-04T20:31:27Z)
pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:53389c9b4a00d7afebb98f7bd9d20348deb1d77ca4baf194f0ae1b582b7e965b
CustomOrigin: Provisioned from oscontainer
Version: 410.8.20190520.0 (2019-05-20T22:55:04Z)
How reproducible:
[root@bed1c2009bd8 /]# ip link add br0 type bridge
[root@bed1c2009bd8 /]# ip link set br0 up
[root@bed1c2009bd8 /]# ip link set br0 type bridge vlan_filtering 1
[root@bed1c2009bd8 /]# bridge vlan show
port vlan ids
br0
1 PVID untagged
Actual results:
[root@bed1c2009bd8 /]# bridge -j vlan show
["br0","vlan":[{"vlan":1,"pvid":null,"untagged":null}]]
Expected results:
The correct output format need structs to be with brackets:
["br0",{"vlan":[{"vlan":1,"pvid":null,"untagged":null}]}]
Additional info:
Also same thing at centos:7 has better output, since network interfaces are struct fields too:
```
[root@69aabb0f165e /]# bridge vlan show
port vlan ids
br0 1 PVID Egress Untagged
[root@69aabb0f165e /]# bridge -j vlan show
{
"br0": [{
"vlan": 1,
"flags": ["PVID","Egress Untagged"
]
}
]
}
```
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-2020:1785
Description of problem: Playing around with linux-bridges and vlan filtering functionality with iproute command 'bridge' we found that it outputs a invalid json and that's a problemn for our processing tools. rpm version: iproute-4.18.0-11.el8.x86_64 os: Red Hat Enterprise Linux CoreOS release 4.1 [core@test-1-mfqwp-master-0 ~]$ rpm-ostree status State: idle AutomaticUpdates: disabled Deployments: * pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fb025ff2b405cf5902a451675cd27a9d702ced7c88b5a33280d42069524874c6 CustomOrigin: Managed by pivot tool Version: 410.8.20190904.0 (2019-09-04T20:31:27Z) pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:53389c9b4a00d7afebb98f7bd9d20348deb1d77ca4baf194f0ae1b582b7e965b CustomOrigin: Provisioned from oscontainer Version: 410.8.20190520.0 (2019-05-20T22:55:04Z) How reproducible: [root@bed1c2009bd8 /]# ip link add br0 type bridge [root@bed1c2009bd8 /]# ip link set br0 up [root@bed1c2009bd8 /]# ip link set br0 type bridge vlan_filtering 1 [root@bed1c2009bd8 /]# bridge vlan show port vlan ids br0 1 PVID untagged Actual results: [root@bed1c2009bd8 /]# bridge -j vlan show ["br0","vlan":[{"vlan":1,"pvid":null,"untagged":null}]] Expected results: The correct output format need structs to be with brackets: ["br0",{"vlan":[{"vlan":1,"pvid":null,"untagged":null}]}] Additional info: Also same thing at centos:7 has better output, since network interfaces are struct fields too: ``` [root@69aabb0f165e /]# bridge vlan show port vlan ids br0 1 PVID Egress Untagged [root@69aabb0f165e /]# bridge -j vlan show { "br0": [{ "vlan": 1, "flags": ["PVID","Egress Untagged" ] } ] } ```