Red Hat Bugzilla – Bug 1551653
Composes taking nearly a day and a half to complete
Last modified: 2018-03-12 19:16:28 EDT
Recent Rawhide and Fedora 28 composes seem to be taking an unreasonably long amount of time to run. Fedora-Rawhide-20180303.n.0 took just over 32 hours (from 2018-03-03 15:55:19 to 2018-03-05 00:05:46: https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20180303.n.0/logs/global/pungi.global.log ).
'Normal' compose time is closer to 8-12 hours, at present, I believe.
Proposing as a Beta blocker per this wording in the criteria:
"A bug is considered a Beta blocker bug if any of the following criteria are met:
Bug hinders execution of required Beta test plans or dramatically reduces test coverage"
Composes taking 3x as long as they should will *clearly* do that; it severely reduces the amount of times we can feasibly respin, and the amount of time QA will have to test any given candidate compose.
Discussed at blocker bug meeting :
AcceptedBlocker (Beta) - this is considered to block the release on the basis that it "hinders execution of required Beta test plans or dramatically reduces test coverage", as per https://fedoraproject.org/wiki/Fedora_28_Beta_Release_Criteria#Beta_Blocker_Bugs
I found one notification  in Fedora-28-20180303.n.1 that may explain
why . Is waiting for a commit sign for 22 hours.
2018-03-05 02:36:30.394652: Commit not signed yet, waiting
2018-03-05 23:11:20.314618: Commit not signed yet, waiting
Part of the slowdown was caused by a bug in Pungi that only appeared when traditional and modular content was included in the compose. That should be fixed in the latest build. Unfortunately that build also introduced another bug that caused a lot of packages to be missing from the compose. Hopefully that would be fixed in pungi-4.1.22-8.fc27 that I'm building now.
per nirik, this is considered sufficiently fixed now. closing.