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 1542391 - calling service reload after starting firewalld stop NM daemon
Summary: calling service reload after starting firewalld stop NM daemon
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks: 1576081
TreeView+ depends on / blocked
 
Reported: 2018-02-06 09:22 UTC by Vladimir Benes
Modified: 2018-05-08 18:32 UTC (History)
10 users (show)

Fixed In Version: systemd-219-55.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1576081 (view as bug list)
Environment:
Last Closed: 2018-04-10 11:25:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
logs (58.45 KB, text/plain)
2018-02-06 09:22 UTC, Vladimir Benes 		no flags Details
journal for NetworkManager restarting (857.60 KB, application/gzip)
2018-02-06 11:54 UTC, Thomas Haller 		no flags Details
systemctl show NetworkManager.service output (4.41 KB, text/plain)
2018-02-06 12:09 UTC, Thomas Haller 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0711 0 None None None 2018-04-10 11:26:25 UTC

Description Vladimir Benes 2018-02-06 09:22:13 UTC 
Description of problem:
NM service goes down after calling systemctl reload NetworkManager after I unmasked firewalld and started it. This is very odd.

 

Version-Release number of selected component (if applicable):
1.10.2-10

How reproducible:
always

Steps to Reproduce:
systemctl unmask firewalld
systemctl start firewalld
systemctl reload NetworkManager

Actual results:
no NM service running

Expected results:
NM should be running and conf reloaded

Additional info:
Comment 2 Vladimir Benes 2018-02-06 09:22:55 UTC 
Created attachment 1391916 [details]
logs
Comment 3 Vladimir Benes 2018-02-06 09:31:40 UTC 
without unmasking it doesn't happen.
Comment 4 Thomas Haller 2018-02-06 11:54:53 UTC 
Created attachment 1392041 [details]
journal for NetworkManager restarting

I replaced NetworkManager.service's ExecStart with:

  ExecStart=/usr/bin/strace -s 2048 -ttt -x -f -D /sbin/NetworkManager --no-daemon

Attached is the journal. We see:


Feb 06 06:38:57 gsm-r5s2-01.wlan.rhts.eng.bos.redhat.com systemd[1]: Reloading.

Feb 06 06:39:08 gsm-r5s2-01.wlan.rhts.eng.bos.redhat.com NetworkManager[2874]: <info>  [1517917148.9204] audit: op="reload" arg="0" pid=2995 uid=0 result="success"

Feb 06 06:39:08 gsm-r5s2-01.wlan.rhts.eng.bos.redhat.com strace[2874]: [pid  2878] 1517917148.963770 restart_syscall(<... resuming interrupted poll ...> <unfinished ...>
Feb 06 06:39:08 gsm-r5s2-01.wlan.rhts.eng.bos.redhat.com strace[2874]: [pid  2880] 1517917148.963792 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=1, si_uid=0} ---
Feb 06 06:39:08 gsm-r5s2-01.wlan.rhts.eng.bos.redhat.com strace[2874]: [pid  2874] 1517917148.963801 <... poll resumed> ) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
Feb 06 06:39:08 gsm-r5s2-01.wlan.rhts.eng.bos.redhat.com strace[2874]: [pid  2880] 1517917148.963813 --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=1, si_uid=0} ---
Feb 06 06:39:08 gsm-r5s2-01.wlan.rhts.eng.bos.redhat.com NetworkManager[2874]: <info>  [1517917148.9641] caught SIGTERM, shutting down normally.




Apparently, systemd is not only executing ExecReload

ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Reload uint32:0

but also sending SIGTERM, which causes NetworkManager to exit.
Comment 5 Thomas Haller 2018-02-06 12:09:43 UTC 
Created attachment 1392044 [details]
systemctl show NetworkManager.service output

Also, the output of `systemctl show NetworkManager`

Note:

ExecReload={ path=/usr/bin/dbus-send ; argv[]=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Reload uint32:0 ; ignore_errors=no ; start_time=[Tue 2018-02-06 06:39:08 EST] ; stop_time=[Tue 2018-02-06 06:39:08 EST] ; pid=2995 ; code=exited ; status=0 }

which matches the time from the previous log, when SIGTERM was received.
Comment 6 Thomas Haller 2018-02-06 12:10:52 UTC 
Reassigning to systemd, to understand why SIGTERM was sent.
Comment 8 Lukáš Nykrýn 2018-02-07 14:10:23 UTC 
fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/194 -> post
Comment 13 errata-xmlrpc 2018-04-10 11:25: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://access.redhat.com/errata/RHBA-2018:0711
Note You need to log in before you can comment on or make changes to this bug.