Bug 1563155

Summary: [abrt] [faf] libteam: ??(): /usr/bin/teamd killed by 11
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: libteamAssignee: Xin Long <lxin>
Status: CLOSED ERRATA QA Contact: LiLiang <liali>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.5CC: dbragalo, kzhang, lxin, network-qe, ralongi, sukulkar
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/beb028b2f9bd27c5f97cdeb20902d29caa0af461/
Whiteboard:
Fixed In Version: libteam-1.27-5.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 11:43:48 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:
Embargoed:

Description Vladimir Benes 2018-04-03 09:42:20 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/beb028b2f9bd27c5f97cdeb20902d29caa0af461/

is something visible from BT? I don't have reproducer.

Comment 2 Xin Long 2018-04-03 11:22:04 UTC
see also: https://bugzilla.redhat.com/show_bug.cgi?id=1547472
identified, and will post upstream the fix asap.

Comment 3 Xin Long 2018-07-02 11:39:06 UTC
*** Bug 1547472 has been marked as a duplicate of this bug. ***

Comment 5 LiLiang 2018-09-07 02:02:05 UTC
Hii Long,

How to verify this? Thanks.

Comment 6 Xin Long 2018-09-07 08:19:31 UTC
(In reply to LiLiang from comment #5)
> Hii Long,
> 
> How to verify this? Thanks.

# ip link add veth1 type veth peer name veth1_peer
# sleep 5 && ip link del veth1 &
# teamd -g -c '{"device":"team0","runner":{"name":"activebackup"}, "ports":{"veth1":{}}}'

Comment 7 LiLiang 2018-09-13 08:13:31 UTC
verified:

[root@hp-dl580g8-02 team]# rpm -qa|grep libteam
libteam-1.27-5.el7.x86_64


[root@hp-dl580g8-02 team]# ip link add veth1 type veth peer name veth1_peer
[root@hp-dl580g8-02 team]# sleep 5 && ip link del veth1 & teamd -g -c '{"device":"team0","runner":{"name":"activebackup"}, "ports":{"veth1":{}}}'
[1] 39106
Using team device "team0".
Using PID file "/var/run/teamd/team0.pid"
This program is not intended to be run as root.
Added loop callback: daemon, 0x55bdc3426410
Added loop callback: libteam_events, 0x55bdc3426410
Added loop callback: workq, 0x55bdc3426410
Using team runner "activebackup".
Using hwaddr_policy "same_all".
usock: Using sockpath "/var/run/teamd/team0.sock"
Added loop callback: usock, 0x55bdc3426410
<ifinfo_list>
 15: team0: ca:c1:f2:c9:89:da: 0 
</ifinfo_list>
<port_list>
</port_list>
veth1: Adding port (found ifindex "14").
1.27 successfully started.
<ifinfo_list>
 15: team0: ca:c1:f2:c9:89:da: 0 
</ifinfo_list>
<port_list>
*14: veth1: down 0Mbit HD 
</port_list>
veth1: Using implicit link watch.
veth1: Got link watch from port config.
veth1: Using sticky "0".
Added loop callback: lw_ethtool_delay, 0x55bdc3427fb0
<ifinfo_list>
*15: team0: *4a:d3:9b:1b:dd:ca: 0 
 14: veth1: 4a:d3:9b:1b:dd:ca: 15 
</ifinfo_list>

<ifinfo_list>
 15: team0: 4a:d3:9b:1b:dd:ca: 0 
*14: veth1: 4a:d3:9b:1b:dd:ca: 15 
</ifinfo_list>
<port_list>
-14: veth1: down 0Mbit HD 
</port_list>
Removed loop callback: lw_ethtool_delay, 0x55bdc3427fb0
<ifinfo_list>
 15: team0: 4a:d3:9b:1b:dd:ca: 0 
</ifinfo_list>
^CGot SIGINT, SIGQUIT or SIGTERM.
Exiting...
Removed loop callback: usock, 0x55bdc3426410
Removed loop callback: workq, 0x55bdc3426410
Removed loop callback: libteam_events, 0x55bdc3426410
Removed loop callback: daemon, 0x55bdc3426410
[1]+  Done                    sleep 5 && ip link del veth1

Comment 9 errata-xmlrpc 2018-10-30 11:43:48 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:3297