Re: Bodhi and "update ejected from the push" errors
On Thu, Feb 10, 2022 at 12:31:15PM +, Sérgio Basto wrote: > On Sat, 2022-01-29 at 11:12 -0800, Kevin Fenzi wrote: > > On Sat, Jan 29, 2022 at 05:38:42PM +, Mattia Verga via devel > > wrote: > > > Recently we're having some (a lot) of errors about updates stuck in > > > Bodhi with errors like "update ejected from the push because Cannot > > > find > > > relevant tag...". > > > > > > I tried to fix some of them myself, and relengs folks are also on > > > this. > > > But since there are so many, I'll post here how to fix yourself. > > > > > > If your Bodhi update is stuck in the "Pending" state, please make > > > sure > > > that all the builds inside the update are tagged in the release > > > candidate tag (which is typically something like > > > 'f35-updates-candidate'). You can check that by clicking on the > > > build(s) > > > name(s) in the right column on the update page. > > > > > > If any build in the update is not properly tagged, you must > > > manually tag > > > it with something like: > > > > > > koji tag-build f35-updates-candidate build-0.1.2-1.fc35 > > > > > Hi, > > Trying to help out here, please check this 2 pages (1), seems the > builds with 2 weeks, were not fixed by the maintainers (yet), could you > fix them ? I've gone through and (I think) fixed all the ones stuck in pending. kevin signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Bodhi and "update ejected from the push" errors
On Sat, 2022-01-29 at 11:12 -0800, Kevin Fenzi wrote: > On Sat, Jan 29, 2022 at 05:38:42PM +, Mattia Verga via devel > wrote: > > Recently we're having some (a lot) of errors about updates stuck in > > Bodhi with errors like "update ejected from the push because Cannot > > find > > relevant tag...". > > > > I tried to fix some of them myself, and relengs folks are also on > > this. > > But since there are so many, I'll post here how to fix yourself. > > > > If your Bodhi update is stuck in the "Pending" state, please make > > sure > > that all the builds inside the update are tagged in the release > > candidate tag (which is typically something like > > 'f35-updates-candidate'). You can check that by clicking on the > > build(s) > > name(s) in the right column on the update page. > > > > If any build in the update is not properly tagged, you must > > manually tag > > it with something like: > > > > koji tag-build f35-updates-candidate build-0.1.2-1.fc35 > > Hi, Trying to help out here, please check this 2 pages (1), seems the builds with 2 weeks, were not fixed by the maintainers (yet), could you fix them ? Thank you (1) https://bodhi.fedoraproject.org/updates/?search==pending=2 https://bodhi.fedoraproject.org/updates/?search==pending=3 > > (obviously you need koji cli to be installed on your system and you > > need > > to be authenticated with kerberos) > > > > After all the builds in the update are tagged you can push the update > > to > > testing. If you just push the update without all the builds properly > > tagged, you'll get another "update ejected from the push" the next > > Bodhi > > composer run. > > > > For updates stuck in the "Testing" state, the quickest solution is to > > unpush the update with the button in Bodhi web interface and then > > re-submit it to testing. > > > > Mattia > > Thanks for that post mattia! > > I'll note that I am pretty convinced this is caused by the koji > duplicate tagging issue, so I have downgraded the koji hubs back to > 1.26.1 until the bug can get sorted out upstream. > > Hopefully that means things will go back to normal as we fix the > already > mistagged things now. > > kevin > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Bodhi and "update ejected from the push" errors
On Sat, Jan 29, 2022 at 05:38:42PM +, Mattia Verga via devel wrote: > Recently we're having some (a lot) of errors about updates stuck in > Bodhi with errors like "update ejected from the push because Cannot find > relevant tag...". > > I tried to fix some of them myself, and relengs folks are also on this. > But since there are so many, I'll post here how to fix yourself. > > If your Bodhi update is stuck in the "Pending" state, please make sure > that all the builds inside the update are tagged in the release > candidate tag (which is typically something like > 'f35-updates-candidate'). You can check that by clicking on the build(s) > name(s) in the right column on the update page. > > If any build in the update is not properly tagged, you must manually tag > it with something like: > > koji tag-build f35-updates-candidate build-0.1.2-1.fc35 > > (obviously you need koji cli to be installed on your system and you need > to be authenticated with kerberos) > > After all the builds in the update are tagged you can push the update to > testing. If you just push the update without all the builds properly > tagged, you'll get another "update ejected from the push" the next Bodhi > composer run. > > For updates stuck in the "Testing" state, the quickest solution is to > unpush the update with the button in Bodhi web interface and then > re-submit it to testing. > > Mattia Thanks for that post mattia! I'll note that I am pretty convinced this is caused by the koji duplicate tagging issue, so I have downgraded the koji hubs back to 1.26.1 until the bug can get sorted out upstream. Hopefully that means things will go back to normal as we fix the already mistagged things now. kevin signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Bodhi and "update ejected from the push" errors
Recently we're having some (a lot) of errors about updates stuck in Bodhi with errors like "update ejected from the push because Cannot find relevant tag...". I tried to fix some of them myself, and relengs folks are also on this. But since there are so many, I'll post here how to fix yourself. If your Bodhi update is stuck in the "Pending" state, please make sure that all the builds inside the update are tagged in the release candidate tag (which is typically something like 'f35-updates-candidate'). You can check that by clicking on the build(s) name(s) in the right column on the update page. If any build in the update is not properly tagged, you must manually tag it with something like: koji tag-build f35-updates-candidate build-0.1.2-1.fc35 (obviously you need koji cli to be installed on your system and you need to be authenticated with kerberos) After all the builds in the update are tagged you can push the update to testing. If you just push the update without all the builds properly tagged, you'll get another "update ejected from the push" the next Bodhi composer run. For updates stuck in the "Testing" state, the quickest solution is to unpush the update with the button in Bodhi web interface and then re-submit it to testing. Mattia ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Update "ejected from the push"
Hi Kevin, On Thu, May 13, 2021 at 10:55 PM Kevin Fenzi wrote: > > Did you by chance add them to the update during the upgrade this > morning? (starting at 10UTC)? It doesn't look like bodhi did the right > thing with the tagging here... I can try and correct things. It was towards the end of the outage window, around 12 UTC. I usually take note of outages that might affect me, but in all honesty this was unplanned and I had completely forgotten about the bodhi upgrade. > In the furture, please do file a releng issue for things like this > (https://pagure.io/releng) I will do my best to remember that, thanks a lot! ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Update "ejected from the push"
On Thu, May 13, 2021 at 10:09:32PM +0200, Alexander Ploumistos wrote: > Hello, > > Can anyone help me figure out what's going on with this update? > https://bodhi.fedoraproject.org/updates/FEDORA-2021-b8551abae2 > > It says that the side-tag is not among a bunch of other tags. It does > exist though. > > What I did was build a package and its dependencies in side-tags for > F33, F34 and F35 (in hindsight that last one was unnecessary). I > submitted the updates in bodhi and after being made aware of the > issue, the F33 update was stopped from moving to stable and I unpushed > the one for F34. I built new versions of the package in the same > side-tags and edited both updates and pushed them to testing again. > > Will this be a problem for this one as well? > https://bodhi.fedoraproject.org/updates/FEDORA-2021-41405921ae > > What should I do? Did you by chance add them to the update during the upgrade this morning? (starting at 10UTC)? It doesn't look like bodhi did the right thing with the tagging here... I can try and correct things. In the furture, please do file a releng issue for things like this (https://pagure.io/releng) kevin signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Update "ejected from the push"
Hello, Can anyone help me figure out what's going on with this update? https://bodhi.fedoraproject.org/updates/FEDORA-2021-b8551abae2 It says that the side-tag is not among a bunch of other tags. It does exist though. What I did was build a package and its dependencies in side-tags for F33, F34 and F35 (in hindsight that last one was unnecessary). I submitted the updates in bodhi and after being made aware of the issue, the F33 update was stopped from moving to stable and I unpushed the one for F34. I built new versions of the package in the same side-tags and edited both updates and pushed them to testing again. Will this be a problem for this one as well? https://bodhi.fedoraproject.org/updates/FEDORA-2021-41405921ae What should I do? ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Update ejected from the push
On Mon, Jun 22, 2020 at 10:00 AM Clement Verna wrote: > > I have deployed bodhi 5.4.0 (https://github.com/fedora-infra/bodhi/releases) > in production today. That should fix the issue with sidetags for normal > releases :-) Thank you! I don't think I'll need to use sidetags until after the data center move, but if something goes wrong, I'll let you know. ___ 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
Re: Update ejected from the push
On Thu, 18 Jun 2020 at 18:35, Kevin Fenzi wrote: > On Thu, Jun 18, 2020 at 07:55:21AM +0200, Alexander Ploumistos wrote: > > These updates, along with a couple of others I submitted 12h ago, just > > appeared in my local mirror. Bodhi still shows everything as > > transitioning from pending to testing and I never got a notification > > about them having moved to testing. Side effect from the data center > > move? > > Well, yes and no? > > The 2 updates you mentioned at the top of the thread were fixed to go in > the next updates push: > https://pagure.io/releng/issue/9532#comment-658452 > > Updates pushes are at 00:14 UTC each day. > > So, they went out with those pushes and now have synced to your local > mirror. :) > > The underlying sidetag issues are being worked on. > I'm not 100% sure of the status... > I have deployed bodhi 5.4.0 (https://github.com/fedora-infra/bodhi/releases) in production today. That should fix the issue with sidetags for normal releases :-) > > kevin > ___ > 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 > ___ 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
Re: Update ejected from the push
On Thu, Jun 18, 2020 at 07:55:21AM +0200, Alexander Ploumistos wrote: > These updates, along with a couple of others I submitted 12h ago, just > appeared in my local mirror. Bodhi still shows everything as > transitioning from pending to testing and I never got a notification > about them having moved to testing. Side effect from the data center > move? Well, yes and no? The 2 updates you mentioned at the top of the thread were fixed to go in the next updates push: https://pagure.io/releng/issue/9532#comment-658452 Updates pushes are at 00:14 UTC each day. So, they went out with those pushes and now have synced to your local mirror. :) The underlying sidetag issues are being worked on. I'm not 100% sure of the status... kevin signature.asc Description: PGP signature ___ 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
Re: Update ejected from the push
These updates, along with a couple of others I submitted 12h ago, just appeared in my local mirror. Bodhi still shows everything as transitioning from pending to testing and I never got a notification about them having moved to testing. Side effect from the data center move? ___ 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
Re: Update ejected from the push
Il 16/06/20 03:47, Kevin Fenzi ha scritto: > > Can you file a releng ticket and we can sort out whats going on. > https://pagure.io/releng/new_issue > > It seems like the sidetag setup has some issues still. ;( > > kevin There have been some improvements in sidetag workflow in Bodhi master branch, which hopefully should resolve some of these issues when 5.3 will be released. Bodhi prod is still on 5.2.2. I think cverna was waiting for a bunch of other PRs to be included in the final version, but now with the datacenter move times are getting larger without the possibility to test in staging first. mattia ___ 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
Re: Update ejected from the push
On Tue, Jun 16, 2020 at 4:24 AM Kevin Fenzi wrote: > > On Tue, Jun 16, 2020 at 03:23:30AM +0200, Alexander Ploumistos wrote: > > On Tue, Jun 16, 2020 at 2:43 AM Alexander Ploumistos > > wrote: > > > > > > The other update doesn't seem to be moving, but at least > > > it hasn't been ejected (yet). > > > > And the second one was just cast out as well. > > Can you file a releng ticket and we can sort out whats going on. > https://pagure.io/releng/new_issue Thanks Kevin, I've opened #9532. ___ 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
Re: Update ejected from the push
On Tue, Jun 16, 2020 at 03:23:30AM +0200, Alexander Ploumistos wrote: > On Tue, Jun 16, 2020 at 2:43 AM Alexander Ploumistos > wrote: > > > > The other update doesn't seem to be moving, but at least > > it hasn't been ejected (yet). > > And the second one was just cast out as well. Can you file a releng ticket and we can sort out whats going on. https://pagure.io/releng/new_issue It seems like the sidetag setup has some issues still. ;( kevin signature.asc Description: PGP signature ___ 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
Re: Update ejected from the push
On Tue, Jun 16, 2020 at 2:43 AM Alexander Ploumistos wrote: > > The other update doesn't seem to be moving, but at least > it hasn't been ejected (yet). And the second one was just cast out as well. ___ 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
Update ejected from the push
Hello, A few hours ago I submitted a couple of updates[0,1] that I had built in side-tags. When I saw that after 7 hours they were still "pending" I got in touch with infra on irc and Mohan gave them a push. I've just received a notification that one of them was ejected from the push because "None of ['f32-updates-testing-pending'] are in" a bunch of other tags. The other update doesn't seem to be moving, but at least it hasn't been ejected (yet). This looks a lot like an issue we had a few months back[2]. Is there something I need to do? Best regards, A. 0. https://bodhi.fedoraproject.org/updates/FEDORA-2020-eec8591e24 1. https://bodhi.fedoraproject.org/updates/FEDORA-2020-44477df31a 2. https://pagure.io/fedora-infrastructure/issue/8477 ___ 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
