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.

This change made it into 7.2 kernel: http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/ip/ipaddress.c?id=ccdcbf35f120c754660b3b3f48fa67cc950a6407

However, the change breaks NetworkManager test suite and possibly anything else that scrapes the ip output.

Please investigate the possibility of coping with the kernel change and retaining the format from ip without change.

The @NONE output should be fixed in the kernel. I filed bug 1238672 for that.

We now return iface@link for more interfaces than before, though. That's a correct behavior and anything scraping ip output needs to be aware of this format. The format is not new, it's just returned for more interfaces now; one example is veth interfaces.

When we talked on IRC, I assumed we are talking about a regression in the iproute package. If the regression is in kernel, and as jbenc says it should be fixed in the kernel, should we even consider it for iproute? Is upstream considering it at all?

I don't think so.
I wasn't sure if this was getting fixed in kernel at the time I reported this.
Feel free to close this.

Thanks for your feedback!