#10478 Build tagged into sidetag twice?
Closed: Upstream by zlopez. Opened by qulogic.

Describe what you would like us to do:


For golang-github-tdewolff-minify, the list of builds on the package page show F36 and F35 builds for the latest version.

However, if you click on the F35 build, it shows complete but the task failed. The task failed with the message:

TagError: build golang-github-tdewolff-minify-2.9.28-1.fc35 already tagged (f35-build-side-49594)

If I then check the history:

$ koji list-history --build=golang-github-tdewolff-minify-2.9.28-1.fc35
Sat Jan 15 04:58:37 2022 golang-github-tdewolff-minify-2.9.28-1.fc35 tagged into f35-build-side-49594 by qulogic [still active]

So it seems like it was tagged in, but then koji tried to tag it in a second time?

This is the final thing to be built together in that side tag, so I'm not sure I actually need it to be tagged in, but I guess some sort of bug occurred that should be fixed.

When do you need this to be done by? (YYYY/MM/DD)


Whenever


It looks like some kind of odd bug in koji. The host's session expired right when it was taking that task, then when it had a session again it tried to take the task again, but it was already done by another builder.

I guess we should collect info and report it to koji developers, but in the mean time it has no harmfull effects I don't think...

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

Metadata