Bug 1596474

Summary: Gnome-shell outputs error messages with GUI Login on the server which uses NetworkManager and bonding
Product: Red Hat Enterprise Linux 7 Reporter: Divya <dbasant>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: bgollahe, cww, fmuellner, jadahl, mboisver, mclasen, myamazak, pgeorgie, rvdwees, tpelka
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: gnome-shell-3.28.3-9.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 12:37:45 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1656436    
Attachments:
Description Flags
Patch fixes the problem
none
Setup of bond connection 1
none
Setup of bond connection 2
none
System journal under RHEL-7.7-20190502.1 none

Description Divya 2018-06-29 05:16:36 UTC
Created attachment 1455422 [details]
Patch fixes the problem

Description of problem:
Gnome-shell outputs error messages with GUI Login on the server which uses NetworkManager and bonding

var/log/messages
--------------------------------------------------------- 
May 14 14:48:52 test journal: JS ERROR: TypeError: item is undefined#012NMConnectionDevice<._activeConnectionChanged@resource:///org/gnome/shell/ui/status/network.js:409#012wrapper@resource:///org/gnome/gjs/modules/lang.js:178

Version-Release number of selected component (if applicable):
gnome-shell-3.26.2-5.el7

How reproducible:
Always

Steps to Reproduce:
1. Add a bond connection for NetworkManager.
2. Reboot the server.


Actual results:
/var/log/messages
May 16 21:51:15 8564J journal: JS ERROR: TypeError: item is undefined#012NMConnectionDevice<._activeConnectionChanged@resource:///org/gnome/shell/ui/status/network.js:409#012wrapper@resource:///org/gnome/gjs/modules/lang.js:178

Expected results:
Sunch error messages should not appear.

Additional info:
Customer confirmed that attached patch fixes the problem for them, i.e error messages does not appear any more.

Comment 3 Florian Müllner 2019-03-11 16:06:53 UTC
This should be fixed by this upstream commit:
https://gitlab.gnome.org/GNOME/gnome-shell/commit/5d61e2563d183272

Comment 5 Jonas Ådahl 2019-03-26 14:35:08 UTC
Reproduced in a VM and the upstream commit mentioned fixes the issue.

Comment 8 Pavlin Georgiev 2019-05-07 14:44:12 UTC
Created attachment 1565247 [details]
Setup of bond connection 1

Comment 9 Pavlin Georgiev 2019-05-07 14:44:40 UTC
Created attachment 1565248 [details]
Setup of bond connection 2

Comment 10 Pavlin Georgiev 2019-05-07 14:45:28 UTC
Created attachment 1565249 [details]
System journal under RHEL-7.7-20190502.1

Comment 11 Pavlin Georgiev 2019-05-07 14:46:25 UTC
TEST SETUP
Distro: RHEL-7.7-20190502.1

Component version: gnome-shell-3.28.3-9.el7


TEST PROCEDURE
1. Install distro RHEL-7.7-20190502.1 on a VM with multiple network interfaces.
2. Log in to a GNOME session.
3. Start nm-connection-editor.
4. Create a bond connection using 2 Ethernet interfaces.
5. Reboot the VM.
6. Log in to a GNOME session.
7. Get the system journal.

The error message does not exist in the journal.


RESULT
Upgrading component: component_name
    from: 3.26.2-5.el7
      to: 3.28.3-9.el7
has fixed the bug.

Comment 13 errata-xmlrpc 2019-08-06 12:37:45 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://access.redhat.com/errata/RHBA-2019:2044