This may be related to the message bus issues affecting fedora infra lately... but I thought I better report it in case some action like rebooting needed for the Koji hub.
But I have had 2 builds at least which took very long to get tagged in koji. For example currently https://koji.fedoraproject.org/koji/taskinfo?taskID=39913318 completed building about 40min ago but the task is still opening pending tagging...
Perhaps I can workaround it by tagging the build manually..
Yes, this is related, no we don't know whats going on yet.
Looks like that build finally failed... I guess try and bump release and try again?
Or wait until we can track down things.
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
For example currently https://koji.fedoraproject.org/koji/taskinfo?taskID=39913318 completed building about 40min ago but the task is still opening pending tagging...
After about 75min:
39913318 build (f30, /rpms/ghc-simple-cmd.git:2f621218147fb1a765e8325ea428147de95c2540): open (buildvm-ppc64le-11.ppc.fedoraproject.org) -> FAILED: GenericError: Build already exists (id=1424802, state=COMPLETE): {'name': 'ghc-simple-cmd', 'task_id': 39913318, 'extra': '{"source": {"original_url": "git+https://src.fedoraproject.org/rpms/ghc-simple-cmd.git#2f621218147fb1a765e8325ea428147de95c2540"}}', 'pkg_id': 27630, 'epoch': None, 'source': 'git+https://src.fedoraproject.org/rpms/ghc-simple-cmd.git#2f621218147fb1a765e8325ea428147de95c2540', 'state': 0, 'version': '0.2.0.1', 'completion_time': None, 'volume_id': 0, 'owner': 56, 'release': '3.fc30', 'start_time': 'NOW'}
Though actually there is no previous existing build.
That worked
I am closing this in favor of ticket #8477 as I am pretty sure this is caused by the same issue... please follow along there.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)