Dear Petr, Thank you for the investigation! I think it happened because the build happened during the freeze.
On Wed, Mar 19, 2025 at 9:24 AM Petr Pisar <ppi...@redhat.com> wrote: > V Wed, Mar 19, 2025 at 08:37:44AM +0100, Dmitry Belyavskiy napsal(a): > > Dear colleagues, > > > > I've built openssh for f42 fixing the latest CVEs a month ago [1]. > > > > The build has passed the gating tests and has positive karma. But it > can't > > be pushed for a while with diagnostics > > > > FEDORA-2025-1e92156b24 ejected from the push because "Cannot find > relevant > > tag for openssh-9.9p1-9.fc42. None of ['f42-updates-candidate', > > 'f42-updates-testing-pending', 'f42-updates-pending'] are in > > ['epel9-next-testing', 'epel10.1-testing', 'eln-updates-testing', > > 'epel8-testing', 'epel9-testing', 'f40-container-updates-testing', > > 'f41-container-updates-testing', 'f41-updates-testing', > > 'f42-updates-testing', 'f40-flatpak-updates-testing', > > 'f40-updates-testing', 'f42-container-updates-testing', > > 'f42-flatpak-updates-testing', 'f41-flatpak-updates-testing', > > 'f43-container-updates-testing', 'epel10.0-testing', > > 'f43-flatpak-updates-testing', 'f43-updates-testing']." > > > > Could anybody please resolve this situation? > > > > [1] https://bodhi.fedoraproject.org/updates/FEDORA-2025-1e92156b24 > > > That build was never in testing (f42-updates-testing): > > $ koji list-history --build openssh-9.9p1-9.fc42 > Tue Feb 18 15:34:51 2025 openssh-9.9p1-9.fc42 tagged into > f42-updates-candidate by dbelyavs [still active] > Tue Feb 18 15:35:54 2025 openssh-9.9p1-9.fc42 tagged into > f42-signing-pending by bodhi > Tue Feb 18 15:36:49 2025 openssh-9.9p1-9.fc42 untagged from > f42-signing-pending by autosign/autosign02.iad2.fedoraproject.org > Tue Feb 18 15:36:49 2025 openssh-9.9p1-9.fc42 tagged into > f42-updates-testing-pending by autosign/autosign02.iad2.fedoraproject.org > [still active] > Wed Feb 19 10:45:06 2025 openssh-9.9p1-9.fc42 tagged into > f42-updates-pending by bodhi > Sat Mar 15 01:15:22 2025 openssh-9.9p1-9.fc42 untagged from > f42-updates-pending by bodhi > Sat Mar 15 01:24:07 2025 openssh-9.9p1-9.fc42 tagged into > f42-updates-pending by bodhi > Sun Mar 16 01:14:11 2025 openssh-9.9p1-9.fc42 untagged from > f42-updates-pending by bodhi > Sun Mar 16 01:18:29 2025 openssh-9.9p1-9.fc42 tagged into > f42-updates-pending by bodhi > Mon Mar 17 01:14:10 2025 openssh-9.9p1-9.fc42 untagged from > f42-updates-pending by bodhi > Mon Mar 17 01:15:27 2025 openssh-9.9p1-9.fc42 tagged into > f42-updates-pending by bodhi > Tue Mar 18 01:14:14 2025 openssh-9.9p1-9.fc42 untagged from > f42-updates-pending by bodhi > Tue Mar 18 01:17:59 2025 openssh-9.9p1-9.fc42 tagged into > f42-updates-pending by bodhi > Wed Mar 19 01:14:13 2025 openssh-9.9p1-9.fc42 untagged from > f42-updates-pending by bodhi > Wed Mar 19 01:18:21 2025 openssh-9.9p1-9.fc42 tagged into > f42-updates-pending by bodhi [still active] > > Which is what bodhi complains. Bodhi history indicates that the build was > auto-pushed to stable just after receving first karma point: > > Comments: bodhi - 2025-02-18 14:34:51 (karma 0) > This update was automatically created > bodhi - 2025-02-18 14:34:53 (karma 0) > This update's test gating status has been changed to 'waiting'. > bodhi - 2025-02-18 15:20:55 (karma 0) > This update's test gating status has been changed to 'failed'. > bodhi - 2025-02-18 16:28:03 (karma 0) > This update's test gating status has been changed to 'waiting'. > bodhi - 2025-02-18 16:50:04 (karma 0) > This update's test gating status has been changed to 'passed'. > pbrobinson - 2025-02-19 09:44:32 (karma 1) > Works fine > bodhi - 2025-02-19 09:44:42 (karma 0) > This update has been submitted for stable by bodhi. There is an > ongoing freeze; this will be pushed to stable after the freeze is > over. > > Web interface reads: > > Autopush Settings > Stable by Karma disabled > > Thresholds > Minimum Karma +1 > Minimum Testing 3 days > > So Bodhi violated its own rules. > > Try retracting the push request for stable and request a push to testing > instead > and after tagging it into f42-updates-testing, try requesting to stable > again. > Alternatively, raise a ticket for relengs to tag the build manually. Pushed to testing, thanks -- Dmitry Belyavskiy
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
