The Bodhi 'release' for EPEL 8 Next has been created with the long name "Epel 8 Next". Bodhi derives the product_version it uses for Greenwave queries from this value: return self.release.long_name.lower().replace(' ', '-'). So the product_version used for Greenwave queries for updates for that release is epel-8-next.

However, that matches nothing in our Greenwave policy. We have catchall 'no requirements' policies that we expect all updates to match on if they don't match on anything else, but they specify product_versions as fedora-*.

For other EPEL releases this is not an issue as their long names start with "Fedora". e.g. the long name for EPEL 8 is "Fedora EPEL 8", so the product_version used for Greenwave queries is fedora-epel-8. This matches the "no requirements" wildcard policies and no other policies, so those updates are never gated.

We could fix this by:

1. Renaming the release to e.g. "Fedora EPEL 8 Next".
2. Adding epel-* to the product_versions for the 'no requirements' policies in Greenwave config.
3. Changing how Bodhi generates the product_version for Greenwave queries somehow.

@kevin suggests going with 1, seems fine to me.