Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When specifying the "USERS=root" property in ifcfg-XXX file of a given network interface, the network gets disabled when last root session exits.
Version-Release number of selected component (if applicable):
NetworkManager-1.4.0-20.el7_3
How reproducible:
Always
Steps to Reproduce:
1. Set up a basic VM
2. Specify "USERS=root" in /etc/sysconfig/network-scripts/ifcfg-eth0 and reboot
3. In a terminal, ping the VM forever
4. Connect to the console of the VM and login as root
5. Logout from root session
Actual results:
Network connectivity is lost (interface gets down)
Expected results:
No loss of connectivity, or explanation of this behaviour in the manual page
This is intended behavior. When you restrict a connection to a certain user, the user must be logged in. It has been this way since ever.
An alternative of connection permissions it to restict access to D-Bus commands via PolicyKit. See `nmcli general permissions` for the permissions you have.
See org.freedesktop.NetworkManager.network-control in /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy
Hi Thomas,
Thank you for confirming this behaviour.
IMO the nm-settings-ifcfg-rh(5) manpage should clearly mention this behaviour when specifying USERS=root, because it has consequences on the shutdown of the OS when NFSv3 mounts are used: typically, the shutdown will just take forever, due to BZ 1312002
Comment 4Beniamino Galvani
2017-07-19 14:28:30 UTC
Created attachment 1301133[details]
[PATCH] libnm-core: clarify the meaning of the connection.permissions property
(In reply to Beniamino Galvani from comment #4)
> Created attachment 1301133[details]
> [PATCH] libnm-core: clarify the meaning of the connection.permissions
> property
lgtm. But breaks make-check for settings-docs.c
Comment 6Beniamino Galvani
2017-07-25 16:09:18 UTC
description: Restrict to certain users the access to this connection, and allow the connection to be active only when at least one of the specified users is logged into an active session.
This should be it. Once more bug filed (#1530977)
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-2018:0778