Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bodhi sends endless spam if two Rawhide packages are built at the same time and the lower NVR one finishes second #3831

Closed
rwmjones opened this issue Dec 5, 2019 · 1 comment

Comments

@rwmjones
Copy link

rwmjones commented Dec 5, 2019

The situation is that I had started the build of nbdkit-1.17.1-2.fc32 and forgotten about it. A new upstream release of nbdkit happened about the same time so I then started a build of nbdkit-1.17.2-1.fc32.

The second (higher NVR) build finished first.

The first (lower NVR) build finished second. This resulted in the following Rawhide update being automatically generated:

https://bodhi.fedoraproject.org/updates/FEDORA-2019-d9458cbc80

However this update then ended up "stuck" in some way. It sent me spam every few minutes about This update cannot be pushed to stable. These builds nbdkit-1.17.1-2.fc32 have a more recent build in koji's f32 tag. See example here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ABRNJT5YPYN2ZM2MB2S2Z3TTF557PYOE/

The spam stopped after about 24 hours for unknown reasons, although in that time I received about 300 messages. However the update still exists.

Also there is no way to delete or obsolete updates from the UI.

@cverna
Copy link
Contributor

cverna commented Dec 5, 2019

This was caused by #3828 with was hot fixed in production. I also have obsoleted the update from the database.
So that should be not be a problem any more.

Sorry about all these email 📪

@cverna cverna closed this as completed Dec 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants