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 1393853 - [NMCI] add team fails after clean install, NM service restart helps
Summary: [NMCI] add team fails after clean install, NM service restart helps
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 13:03 UTC by Vladimir Benes
Modified: 2017-08-01 09:19 UTC (History)
12 users (show)

Fixed In Version: NetworkManager-1.8.0-0.2.git20170215.1d40c5f4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 09:19:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
[PATCH] team: ignore SIGPIPE when spawning teamd (3.62 KB, patch)
2016-11-10 14:21 UTC, Beniamino Galvani
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2299 0 normal SHIPPED_LIVE Moderate: NetworkManager and libnl3 security, bug fix and enhancement update 2017-08-01 12:40:28 UTC

Description Vladimir Benes 2016-11-10 13:03:30 UTC
Description of problem:
basic team master adding via nmcli con add type team leads to device disappear as it looks like teamd dies. Not exactly sure the steps to reproduce but I can get broken env from our tests quite easily but it looks it's caused by systemctl restart journald.


Version-Release number of selected component (if applicable):
teamd-1.25-4.el7.x86_64
NetworkManager-1.4.0-12.el7.x86_64
systemd-219-30.el7.x86_64

How reproducible:
always after install

Steps to Reproduce:
1.install the machine
2.restart NM service
3.restart journald service

Actual results:
NM cannot create team as teamd dies

Expected results:
no issue with team creation

Additional info:
restarting NM fixes the issue

Comment 1 Beniamino Galvani 2016-11-10 13:21:28 UTC
teamd terminates with an error because stderr in detached after the
restart of systemd-journald. NM logs:

  [1478776054.0408] device[0x7f44e8864c40] (team2): running: /usr/bin/teamd -o -n -U -D -N -t team2 -gg
  [1478776054.0695] device (team2): Activation: (team) started teamd [pid 31824]...
  [1478776054.0696] device[0x7f44e8864c40] (team2): activation-stage: complete activate_stage1_device_prepare,2 (id 2653)
  [1478776054.0697] kill child process 'teamd' (31743): terminated normally with status 0 (31712 usec elapsed)
  [1478776054.0698] device[0x7f44e8864c40] (team2): teamd not on D-Bus (ignored)
  [1478776054.0701] device[0x7f44e8864c40] (team2): teamd died with status 13
  [1478776054.0701] device (team2): teamd process quit unexpectedly; failing activation

strace of teamd:

  [...]
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f55cba69000
  read(3, "################################"..., 4096) = 1130
  read(3, "", 4096)           = 0
  close(3)                    = 0
  munmap(0x7f55cba69000, 4096) = 0
  mkdir("/var/run/teamd/", 0755) = -1 EEXIST (File exists)
  open("/dev/urandom", O_RDONLY) = 3
  read(3, "\275}M\271", 4)    = 4
  close(3)                    = 0
  write(2, "Using team device \"team2\".", 28) = -1 EPIPE (Broken pipe)
  --- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=23889, si_uid=0} ---

systemd-219 shipped with RHEL 7	should include this commit [1] which
temporarily stores fds to pid1 while restarting journald and so this
situation should be handled well:

  [1] https://github.com/systemd/systemd/commit/13790add4bf648fed8163

But apparently it is not working. I'm reassigning this to systemd
for analysis.

Comment 2 Beniamino Galvani 2016-11-10 14:21:10 UTC
Created attachment 1219409 [details]
[PATCH] team: ignore SIGPIPE when spawning teamd

This is a workaround for NM to let the child ignore SIGPIPE and survive
the lack of stdout/stderr if journald was restarted. Anyway, it's
still a sub-optimal solution because any output of the child will be
lost.

Ideally this should be solved in systemd by properly restoring the
file descriptors after the restart of journald.

Comment 3 Thomas Haller 2016-11-10 14:48:05 UTC
(In reply to Beniamino Galvani from comment #2)
> Created attachment 1219409 [details]
> [PATCH] team: ignore SIGPIPE when spawning teamd

lgtm

Comment 10 errata-xmlrpc 2017-08-01 09:19:37 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/RHSA-2017:2299


Note You need to log in before you can comment on or make changes to this bug.