Bug 1674763
Summary: | containerd: FTBFS in Fedora rawhide/f30 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
Component: | containerd | Assignee: | Carl George <carl> | ||||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | rawhide | CC: | carl | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2019-02-28 20:13:40 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: | |||||||||||
Bug Depends On: | 1680040 | ||||||||||
Bug Blocks: | 1674516 | ||||||||||
Attachments: |
|
Description
Fedora Release Engineering
2019-02-11 16:59:42 UTC
Created attachment 1529579 [details]
build.log
file build.log too big, will only attach last 1024 bytes
Created attachment 1529580 [details]
root.log
file root.log too big, will only attach last 1024 bytes
Created attachment 1529581 [details]
state.log
The rebuild failed on ppc64le and aarch64. I can't reproduce the aarch64 failure, but ppc64le fails consistently in scratch builds. The result is the same if I update to the latest 1.2.3 upstream source. I've reported it upstream. https://github.com/containerd/containerd/issues/3005 If upstream is unresponsive I can disable the tests on ppc64le to get it to pass for now. Looks like it's an golang issue. Rawhide is using golang 1.12 beta2, which introduced the bug. https://github.com/golang/go/issues/30283 |