Bug 1734883

Summary: koji builds fail on s390x sometimes, SRPM cannot be unpacked: cpio: read failed - Inappropriate ioctl for device
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: kojiAssignee: Mike McLean <mikem>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bjorn, dennis, jkeating, kevin, mikem, puiterwijk, rjones
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-25 18:32:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2019-07-31 16:07:14 UTC
GtkAda3 failed to build from source in Fedora rawhide/f31

https://koji.fedoraproject.org/koji/taskinfo?taskID=36631590


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix GtkAda3 at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
GtkAda3 will be orphaned. Before branching of Fedora 32,
GtkAda3 will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source

Comment 1 Fedora Release Engineering 2019-07-31 16:07:16 UTC
Created attachment 1595220 [details]
build.log

Comment 2 Fedora Release Engineering 2019-07-31 16:07:18 UTC
Created attachment 1595221 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2019-07-31 16:07:19 UTC
Created attachment 1595222 [details]
state.log

Comment 4 Ben Cotton 2019-08-13 17:10:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 5 Ben Cotton 2019-08-13 18:47:35 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 6 Richard W.M. Jones 2019-08-19 18:00:07 UTC
Here's another s390x build which failed in the same way:

https://koji.fedoraproject.org/koji/taskinfo?taskID=37162999

Note ignore the build.log, the error is actually in root.log:

https://kojipkgs.fedoraproject.org//work/tasks/2999/37162999/root.log

As far as I know the tarball for this package contains only regular
files and directories:

$ zcat nbdkit-1.13.8.tar.gz | tar tvvf - | grep -Ev '^[-d]'
(no output)

Comment 7 Richard W.M. Jones 2019-09-06 13:24:49 UTC
Another s390x failure.  Again, look at the root.log file, not the
build.log file:

https://koji.fedoraproject.org/koji/taskinfo?taskID=37498591

Comment 8 Fedora Release Engineering 2019-09-22 04:22:56 UTC
Dear Maintainer,

your package has not been built successfully in 31. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your package
can be orphaned if this bug remains in NEW state more than 8 weeks.

A week before the mass branching of Fedora 32 according to the schedule [3],
any packages which still have open FTBFS bugs from Fedora 31 will be retired.

[1] https://fedoraproject.org/wiki/Updates_Policy
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedoraproject.org/wiki/Releases/32/Schedule

Comment 9 Björn Persson 2019-09-24 13:45:46 UTC
Is that Koji that the script is going to retire, or GTKada?

I'm unlinking the trackers, hoping that that will stop the script from kicking out either package.

Comment 10 Kevin Fenzi 2020-04-25 18:32:43 UTC
We are tracking this upstream in https://pagure.io/koji/issue/1974

It seems to be happening less often now, but we have debugging in place to try and isolate it. 

If you hit this, you should be able to resubmit and get a good build. 
If not and something urgent is happening, please contact fedora-releng. 

Otherwise, sorry for the hassle and hopefully we will track this down and fix it soon.