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.

Description of problem:
`self.dev` can be null for inactivate virtual interfaces such as bridges, bonds, and vlans, but the code expects it to be non-null

Version-Release number of selected component (if applicable):
122-1

How reproducible:
Always

Additional info:
Fixed upstream in 6bedd6b7af14be4d8928ea66606ff579898f5d15

Upstream master commit
https://github.com/cockpit-project/cockpit/commit/6961a619a3d9012f7a2ac19e8c235e43a2cd216d

Is this actually a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1390605 ?

It is related, but not a duplicate.

https://bugzilla.redhat.com/show_bug.cgi?id=1390605 has to do with a device not activating properly, because the default parameters in the networkmanager changed (or were different in the dbus API), which is a functional bug.

This bug leads to an actual javascript error and an "Ooops" in Cockpit, which might not affect already released versions of Cockpit.

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://rhn.redhat.com/errata/RHBA-2016-2888.html