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.
Bug 1457691 - GNOME 3 control-center cannot setup a network interface
Summary: GNOME 3 control-center cannot setup a network interface
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: control-center
Version: 7.4
Hardware: ppc64le
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rui Matos
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1456511
TreeView+ depends on / blocked
 
Reported: 2017-06-01 07:12 UTC by Pavlin Georgiev
Modified: 2017-08-01 22:40 UTC (History)
5 users (show)

Fixed In Version: 3.22.2-5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:40:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Debug log (9.16 KB, text/plain)
2017-06-01 07:12 UTC, Pavlin Georgiev 		no flags Details
Video record (154.93 KB, application/octet-stream)
2017-06-01 07:15 UTC, Pavlin Georgiev 		no flags Details
Information about the host (50.05 KB, text/plain)
2017-06-01 07:16 UTC, Pavlin Georgiev 		no flags Details
Diagnostic files from PPC64 (206.24 KB, application/zip)
2017-06-01 07:51 UTC, Pavlin Georgiev 		no flags Details
Diagnostic files from x86_64 VM (209.57 KB, application/zip)
2017-06-01 07:53 UTC, Pavlin Georgiev 		no flags Details
Diagnostic files from x86_64 VM (68.45 KB, application/zip)
2017-06-13 12:37 UTC, Pavlin Georgiev 		no flags Details
Diagnotic files from x86_64 (29.63 KB, application/zip)
2017-06-22 11:32 UTC, Pavlin Georgiev 		no flags Details
Daignosti files from x86_64 on a laptop (35.78 KB, application/zip)
2017-06-22 11:34 UTC, Pavlin Georgiev 		no flags Details
Daignostic files from x86_64 on a desktop PC (399.18 KB, application/zip)
2017-06-22 14:45 UTC, Pavlin Georgiev 		no flags Details
Diagnostic files from PPC64LE (435.81 KB, application/zip)
2017-06-22 15:57 UTC, Pavlin Georgiev 		no flags Details
Show Obsolete (2) View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 783998 0 Normal RESOLVED network: Fix critical when veth1 has no UUID 2020-12-18 09:37:53 UTC
Red Hat Product Errata RHBA-2017:2096 0 normal SHIPPED_LIVE control-center, accountsservice, gnome-settings-daemon, libgnomekbd update 2017-08-01 19:36:13 UTC

Description Pavlin Georgiev 2017-06-01 07:12:34 UTC 
Created attachment 1284017 [details]
Debug log

Description of problem:
GNOME 3 control-center cannot setup a network interface of type Ethernet (Veth).

Version-Release number of selected component (if applicable):
gnome-session-3.22.3-3.el7.ppc64le
control-center-3.22.2-3.el7.ppc64le
NetworkManager-1.8.0-3.el7.ppc64le


How reproducible:
Always

Steps to Reproduce:
1. Start control-center
2. Open section "Network"
3. Select a network interface of type Veth.

Actual results:
A dialog with error appears.


Expected results:
A new GUI frame to set up the network interface should appear.


Additional info:
I ran control-center with debug messages, on the foreground.
Comment 3 Pavlin Georgiev 2017-06-01 07:15:05 UTC 
Created attachment 1284018 [details]
Video record
Comment 4 Pavlin Georgiev 2017-06-01 07:16:37 UTC 
Created attachment 1284019 [details]
Information about the host
Comment 5 Pavlin Georgiev 2017-06-01 07:51:52 UTC 
Created attachment 1284029 [details]
Diagnostic files from PPC64

The same effect appears when testing on architecture PPC64.
Comment 6 Pavlin Georgiev 2017-06-01 07:53:34 UTC 
Created attachment 1284030 [details]
Diagnostic files from x86_64 VM

The same effect appears on architecture x86_64 VM, but not on a physical machine. On the physical machine it is OK.
Comment 7 Bastien Nocera 2017-06-06 07:01:50 UTC 
(gnome-control-center:31072): libnm-CRITICAL **: ((libnm-core/nm-connection.c:1815)): assertion '<dropped>' failed

Please run this with the environment variable "G_DEBUG=fatal_warnings" and gather a backtrace of the critical error?

Looks like a NetworkManager library is causing the critical error.
Comment 8 Pavlin Georgiev 2017-06-13 12:36:42 UTC 
I tested on a VM: qe-dell-ovs5-vm-9
DISTRO: RHEL-7.4-20170609.n.0 Workstation x86_64. 

I created several Veth network interfaces by using a script.
When I open control-center and select "Network", I choose Veth1, and click properties.
Then control-center stops working.
Comment 9 Pavlin Georgiev 2017-06-13 12:37:23 UTC 
Created attachment 1287267 [details]
Diagnostic files from x86_64 VM
Comment 10 Vladimir Benes 2017-06-14 08:40:07 UTC 
(In reply to Bastien Nocera from comment #7)
> (gnome-control-center:31072): libnm-CRITICAL **:
> ((libnm-core/nm-connection.c:1815)): assertion '<dropped>' failed
> 
> Please run this with the environment variable "G_DEBUG=fatal_warnings" and
> gather a backtrace of the critical error?
> 
> Looks like a NetworkManager library is causing the critical error.

Bastien, I would expect something like this:
https://paste.fedoraproject.org/paste/9ZLV1RwAjSnLtbYAST2h9Q

steps:
sudo ip link add veth0 type veth peer name veth1
sudo ip link set dev veth0 up
sudo ip link set dev veth1 up
nmcli device set veth1 managed yes
nmcli device set veth0 managed yes
nmcli connection add type ethernet ifname veth0 con-name ethie

now open c-c and press gear icon for both devices, it works for veth0 but there is a crash for veth1

Not sure who should make the check if device has a connection or not. Maybe NM (or it's libs) should take care about it.
Comment 11 Bastien Nocera 2017-06-20 13:24:49 UTC 
It's not a crash, but a critical. It only happens with this version of gnome-control-center and the associated libnm, but not with a more recent g-c-c and libnma.

I've attached a patch to make it throw a warning earlier to avoid the critical, but the device still doesn't have a UUID, which I don't think g-c-c can do anything about:
https://bugzilla.gnome.org/show_bug.cgi?id=783998

I think we should just hide those types of devices in g-c-c, it's not the interface to set up and manage virtual clusters.
Comment 14 Pavlin Georgiev 2017-06-22 11:32:27 UTC 
Created attachment 1290656 [details]
Diagnotic files from x86_64

I tested the newest version for control-center on a VM.

What is the hardware platform?
    x86_46, VM

What is the OS version, control-center version?
    RHEL 7.4 Workstation latest
    control-center-3.22.2-5.el7

What are the network interfaces: number and type?
    1 Ethernet interface
    9 Veth interfaces

    Veth interafaces are dynamically created via a script.
    # Create a network namespace for veth setup
    ip netns add vethsetup

    # Create 'internal' veth devices and hide their peers inside namespace
    for X in $(seq 1 9); do
        ip link add eth${X} type veth peer name eth${X}p
        ip link set eth${X}p netns vethsetup
    done

How do they appear in control-center?
    Ethernet interface is visible in the list. Veth interfaces are not visible.
Comment 15 Pavlin Georgiev 2017-06-22 11:34:54 UTC 
Created attachment 1290657 [details]
Daignosti files from x86_64 on a laptop

I tested the newest version of control-center on a laptop.

What is the hardware platform?
    Physical machine - laptop Dell Precision M4700, x86_64.

What is the OS version, control-center version?
    RHEL 7.4 Workstation latest
    control-center-3.22.2-5.el7

What are the network interfaces: number and type?
    1 Ethernet interface - physical
    9 Veth interfaces

    Veth interafaces are dynamically created via a script.
    # Create a network namespace for veth setup
    ip netns add vethsetup

    # Create 'internal' veth devices and hide their peers inside namespace
    for X in $(seq 1 9); do
        ip link add eth${X} type veth peer name eth${X}p
        ip link set eth${X}p netns vethsetup
    done

How do they appear in control-center?
    Ethernet interface is visible in the list. Veth interfaces are not visible.
Comment 17 Pavlin Georgiev 2017-06-22 14:45:21 UTC 
Created attachment 1290747 [details]
Daignostic files from x86_64 on a desktop PC

What is the hardware platform?
    Physical machine - desktop PC, x86_64

What is the OS version, control-center version?
    RHEL 7.4 Workstation Latest
    control-center-3.22.2-5.el7

What are the network interfaces: number and type?
    1 Ethernet - physical
    10 Veth interafaces

    Veth interfaces are created dynamically via a script.

How do they appear in control-center?
    I see all Veth interfaces in control-center.
Comment 18 Bastien Nocera 2017-06-22 15:24:01 UTC 
They should not appear. If they appear, attach the output of "gnome-control-center -v network" here.
Comment 19 Pavlin Georgiev 2017-06-22 15:57:59 UTC 
Created attachment 1290763 [details]
Diagnostic files from PPC64LE

What is the hardware platform?
    Physical machine, PPC64LE

What is the OS version, control-center version?
    RHEL 7.4 Workstation Latest
    control-center-3.22.2-5.el7

What are the network interfaces: number and type?
    1 Ethernet - physical
    10 Veth interafaces

    Veth interfaces are created dynamically via a script.

How do they appear in control-center?
    Ethernet interface is visible in the list. Veth interfaces are not visible.
Comment 20 Tomas Pelka 2017-06-23 05:36:29 UTC 
Pavlin in c11 Bastien clearly said that Veth devices should be ignored by g-c-c, in other words they should not appear in the list. What is still unclear?

-Tom
Comment 21 Pavlin Georgiev 2017-06-23 06:36:39 UTC 
I tested control-center on the latest RHEL 7.4
by using a physical machine having x86_64.
Veth interfaces are present, but does not appear in control-center.

Upgrading the component: control-center
    from version: 3.22.2-3.el7
      to version: 3.22.2-5.el7
has fixed the bug.
Comment 22 errata-xmlrpc 2017-08-01 22:40:58 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-2017:2096
Note You need to log in before you can comment on or make changes to this bug.