#8430 Bodhi failed to get candidate builds
Closed: Upstream by kevin. Opened by salimma.

Describe what you would like us to do:

I can't create a new update from https://bodhi.fedoraproject.org/updates/new, since Bodhi always timed out getting updates from Koji and errored out with "Error encountered getting candidate builds from koji"

Tried on both Firefox 70.0.1 and Chrome 78.0.3904.108

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

Ideally ASAP

Screenshot_from_2019-12-01_22-10-38.png


This also fails using the CLI

bodhi updates new --type bugfix --bugs 1759404 --close-bugs --notes "Fix bugs in jumphost connections" et-6.0.4-1.fc30,et-6.0.4-1.f31
Username: salimma
Password: 
Build does not exist: et-6.0.4-1.f31
You may not specify an empty list of builds.
ACL validation mechanism was unable to determine ACLs.

The builds do show up here:
https://apps.fedoraproject.org/packages/et/builds/

Koji doesn't seem to know about this build:

$ koji buildinfo et-6.0.4-1.f31
No such build: et-6.0.4-1.f31

Your nevr are incorrect, you want et-6.0.4-1.fc30 and et-6.0.4-1.fc31, cf .fc30 and .fc31

Ouch, typo on my part. So the CLI does work, but the web UI still seems to be broken even now.

 bodhi updates new --type bugfix --bugs 1759404 --close-bugs --notes "Fix bugs in jumphost connections" et-6.0.4-1.fc30,et-6.0.4-1.fc31
 et-6.0.4-1.fc30                          rpm        pending   2019-12-03 (0)
 et-6.0.4-1.fc31                          rpm        pending   2019-12-03 (0)
Caveats:
Your update is being split into 2, one for each release.
The number of stable days required was set to the mandatory release value of 7 days
The number of stable days required was set to the mandatory release value of 7 days

Metadata Update from @mizdebsk:
- Issue tagged with: bodhi

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

It's kind of slow, but it works here... can you please retry now?

If it persists, can you file a upstream bug at https://github.com/fedora-infra/bodhi/issues on it?

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

Metadata