Bug 1383828

Summary:	Cannot provision network with nmcli from firstboot module
Product:	[Fedora] Fedora	Reporter:	David Woodhouse <dwmw2>
Component:	NetworkManager	Assignee:	Lubomir Rintel <lkundrak>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	dcbw, fgiudici, lkundrak
Target Milestone:	---
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:	2017-08-08 19:23:38 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 David Woodhouse 2016-10-11 21:44:22 UTC

We have a firstboot module which joins a system to the corporate AD domain, obtains certificates and provisions VPN and 802.1x connections. I finally got round to fixing it *not* to just drop files into /etc/NetworkManager/system-connections and /etc/sysconfig/network-scripts, and instead use nmcli as it should.

It doesn't work. The nmcli invocation from firstboot fails with:

 *** nmcli-CRITICAL **: Error: Could not create NMClient object: Timeout was reached.

I know this wants to be converted to initial-setup instead of firstboot, but I believe that runs at basically the same time so will suffer the same problem.

NetworkManager *is* running, and I certainly have network connectivity. So what's going wrong?

Comment 1 David Woodhouse 2016-10-11 23:39:44 UTC

Looks like it's SELinux policy preventing NetworkManager from *replying* to nmcli, when nmcli is running from firstboot:

type=USER_AVC msg=audit(1476228143.315:202): pid=640 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc:  denied  { send_msg } for msgtype=method_return dest=:1.29 spid=752 tpid=1294 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:system_r:firstboot_t:s0 tclass=dbus  exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'

Comment 2 Fedora End Of Life 2017-07-25 23:26:09 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 19:23:38 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.