Bug 1394667

Summary: regression when activating virtual interfaces
Product: Red Hat Enterprise Linux 7 Reporter: Dominik Perpeet <dperpeet>
Component: cockpitAssignee: Dominik Perpeet <dperpeet>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: dperpeet, jscotka, stefw
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-06 17:44:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dominik Perpeet 2016-11-14 07:57:36 UTC
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

Comment 1 Dominik Perpeet 2016-11-14 08:39:20 UTC
Upstream master commit
https://github.com/cockpit-project/cockpit/commit/6961a619a3d9012f7a2ac19e8c235e43a2cd216d

Comment 2 Stef Walter 2016-11-14 08:56:33 UTC
Is this actually a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1390605 ?

Comment 3 Dominik Perpeet 2016-11-14 13:39:42 UTC
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.

Comment 7 errata-xmlrpc 2016-12-06 17:44:34 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://rhn.redhat.com/errata/RHBA-2016-2888.html