#9532 Updates created in side-tags ejected from push
Closed: Fixed by mohanboddu. Opened by alexpl.

  • Describe the issue

I created updates FEDORA-2020-44477df31a and FEDORA-2020-eec8591e24 with packages built in side-tags, f32-build-side-24536 and f31-build-side-2453. 7 hours after submitting the updates, I saw that they were still "pending", so I contacted infra and Mohan pushed them to testing. 3 hours later I got a notification that one of the updates was ejected from the push and shortly after that the same happened with the other one. Bodhi gives the following reason:

FEDORA-2020-44477df31a ejected from the push because "Cannot find relevant tag for qwt5-qt5-5.2.3a-4.20190819giteeacc44.fc32. None of ['f32-updates-testing-pending'] are in ['f32-container-updates-candidate', 'f33-updates-candidate', 'f32-modular-updates-candidate', 'f32-flatpak-updates-candidate', 'dist-6E-epel-testing-candidate', 'epel7-testing-candidate', 'dist-5E-epel-testing-candidate', 'f27-modular-updates-candidate', 'f33-container-updates-candidate', 'eln-updates-candidate', 'f30-modular-updates-candidate', 'f28-modular-updates-candidate', 'f28-container-updates-candidate', 'f30-container-updates-candidate', 'epel8-testing-candidate', 'f30-flatpak-updates-candidate', 'f31-modular-updates-candidate', 'f31-container-updates-candidate', 'f31-flatpak-updates-candidate', 'f29-modular-updates-candidate', 'f29-container-updates-candidate', 'f29-flatpak-updates-candidate', 'f22-updates-candidate', 'f21-updates-candidate', 'f25-updates-candidate', 'f24-updates-candidate', 'f23-updates-candidate', 'f26-updates-candidate', 'f27-updates-candidate', 'f28-updates-candidate', 'f32-updates-candidate', 'f30-updates-candidate', 'f31-updates-candidate', 'f29-updates-candidate', 'el8-modular-updates-candidate']."

It's only the second time I've used side-tags and since the first time my updates got stuck again (but bot ejected), I was wondering if I'm using the side-tags wrong.

  • When do you need this? (YYYY/MM/DD)

As soon as it's convenient, given the move and everything.

  • When is this no longer needed or useful? (YYYY/MM/DD)

Even if there is a new SciDAVis release, I will still need the qwt5-qt5 builds to be in the buildroot, as it is a BR for the 2.x branch.

  • If we cannot complete your request, what is the impact?

:broken_heart: :sob:


Hi, I have resubmitted your updates. I am not sure but this seems to be a glitch on our side possibly in bodhi.

Thank you Tomáš. I see that it's been over 3h now and they still haven't moved, which is making me a bit nervous…

@cverna Not sure whats going on, but side tags builds are not getting tagged properly when the update is created.

Can you take a look?

Metadata Update from @mohanboddu:
- Issue tagged with: groomed, high-gain, medium-trouble

Closing this ticket as it seems to have fixed.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata