Bug 1244440

Summary: Failed start transient unit: Input/output error
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Jakub Prokes <jprokes>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.1CC: jprokes, jscotka, lnykryn, systemd-maint-list, todoleza
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: ppc64   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-219-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 15:07:46 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 2015-07-18 21:05:06 UTC
Description of problem:
[root@hostname ~]# systemd-run --unit teamd teamd --team-dev=team0
Running as unit teamd.service.
Failed start transient unit: Input/output error

blocking some NM test, happening just on ppc64 (ppc64le is OK)
 
Version-Release number of selected component (if applicable):
teamd-1.17-1.el7.ppc64
systemd-208-20.el7_1.6.ppc64
systemd-sysv-208-20.el7_1.6.ppc64
kernel-3.10.0-229.10.1.el7_1.ppc64
systemd-libs-208-20.el7_1.6.ppc64
libgudev1-208-20.el7_1.6.ppc64

How reproducible:
always

Steps to Reproduce:
1.systemd-run --unit teamd teamd --team-dev=team0

Actual results:
Running as unit teamd.service.
Failed start transient unit: Input/output error

Expected results:
team0 device

Additional info:

Comment 1 Lukáš Nykrýn 2015-07-20 07:56:36 UTC
It seems to work fine with 7.2 systemd

[root@notas ~]# rpm -q systemd
systemd-219-8.el7.x86_64
[root@notas ~]# systemd-run --unit teamd teamd --team-dev=team0
Running as unit teamd.service.
[root@notas ~]# systemctl status teamd.service
● teamd.service - /bin/teamd --team-dev=team0
   Loaded: loaded (/run/systemd/system/teamd.service; static; vendor preset: disabled)
  Drop-In: /run/systemd/system/teamd.service.d
           └─50-Description.conf, 50-ExecStart.conf
   Active: active (running) since Po 2015-07-20 09:56:00 CEST; 8s ago
 Main PID: 3621 (teamd)
   CGroup: /system.slice/teamd.service
           └─3621 /bin/teamd --team-dev=team0

čec 20 09:56:00 notas systemd[1]: Started /bin/teamd --team-dev=team0.
čec 20 09:56:00 notas systemd[1]: Starting /bin/teamd --team-dev=team0...
čec 20 09:56:00 notas teamd[3621]: 1.15 successfully started.

Comment 2 Vladimir Benes 2015-07-20 08:19:01 UTC
I clearly stated in architecture and in comment that it's just happening on ppc64, didn't I? Reopening. I hitted this issue during z stream testing of NM during this weekend.

Comment 3 Vladimir Benes 2015-07-20 08:20:45 UTC
(In reply to Vladimir Benes from comment #2)
> I clearly stated in architecture 
I meant Hardware field, sorry for confusion.

Comment 4 Lukáš Nykrýn 2015-07-20 08:23:55 UTC
Sorry, can you please retest this with the latest systemd?

Comment 5 Vladimir Benes 2015-07-20 09:31:36 UTC
[root@ibm-p8-kvm-01-guest-08 ~]# systemd-run --unit teamd teamd --team-dev=team0
Running as unit teamd.service.
[root@ibm-p8-kvm-01-guest-08 ~]# rpm -q kernel systemd teamd
kernel-3.10.0-295.el7.ppc64
systemd-219-8.el7.ppc64
teamd-1.17-1.el7.ppc64
[root@ibm-p8-kvm-01-guest-08 ~]# ip a s team0
4: team0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether da:e2:f8:dd:c0:ec brd ff:ff:ff:ff:ff:ff

so it seems to work. should I close or do we want to fix it for z stream? do we plan some release like this in 7.1 timeframe?

Comment 6 Lukáš Nykrýn 2015-07-20 09:46:45 UTC
Lets close it, this was fixed by some major reworks in systemd and it is not a z-stream material unless there is super-critical customer ticket.

Comment 7 Lukáš Nykrýn 2015-07-20 13:49:05 UTC
*** Bug 1243918 has been marked as a duplicate of this bug. ***

Comment 8 Tomas Dolezal 2015-07-20 14:01:38 UTC
Lukasi,
this is not working in current release. Please change the close reason. Also, I think this should be tested (similarly as per bz1243918). How do we get to test this if it's closed?

Comment 11 errata-xmlrpc 2015-11-19 15:07:46 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://rhn.redhat.com/errata/RHBA-2015-2092.html