Bug 1915803
Summary: | ceph fails to build with ???:0 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Miro Hrončok <mhroncok> |
Component: | ceph | Assignee: | Kaleb KEITHLEY <kkeithle> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | adeza, branto, danmick, david, fedora, i, josef, kkeithle, loic, mhroncok, ramkrsna, steve, thrnciar |
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: | 2021-01-14 12:55:50 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1868278, 1890881 |
Description
Miro Hrončok
2021-01-13 13:04:15 UTC
I suspect: https://koschei.fedoraproject.org/affected-by/gcc-c++?epoch1=0&version1=11.0.0&release1=0.11.fc34&epoch2=0&version2=11.0.0&release2=0.12.fc34&collection=f34 But I'm not sure :( (In reply to Miro Hrončok from comment #1) > I suspect: > > https://koschei.fedoraproject.org/affected-by/gcc-c++?epoch1=0&version1=11.0. > 0&release1=0.11.fc34&epoch2=0&version2=11.0.0&release2=0.12. > fc34&collection=f34 > > But I'm not sure :( Note: building also breaks with python3-9, so it's not related to python-3.10. When I ran the build by hand I got a gcc internal error that doesn't appear in the koji build.log files of any of the scratch builds that I did. In function ‘std::string rgw::lc::s3_expiration_header(DoutPrefixProvider*, const rgw_obj_key&, const RGWObjTags&, const real_time&, const std::map<std::__cxx11::basic_string<char>, ceph::buffer::v15_2_0::list>&)’: Segmentation fault 2123 | std::string s3_expiration_header( | ^~~~~~~~~~~~~~~~~~~~ 0x15ff5c9 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char const*, __va_list_tag (*) [1], diagnostic_t) ???:0 0xfc93b7 internal_error(char const*, ...) ???:0 0x937254 crash_signal(int) ???:0 A segv but no core file according to coredumpctl. Why not, my ulimit -c is unlimited. I'm not seeing how this is a ceph bug. ceph builds with gcc-11.0.0-0.11, but not gcc-11.0.0-0.12? I'd say that's almost certainly a bug in -0.12 and I suspect it's a dupe of the bzs in https://bugzilla.redhat.com/show_bug.cgi?id=1915803#c2. I see there's a new build (-0.13). Will try a koji scratch build with that. Otherwise I'll give this a day and then close it as a dupe. And I see that ceph builds are back to normal after -0.13 landed. I'm closing this as a dupe. *** This bug has been marked as a duplicate of bug 1915400 *** |