The API didn't work and failed with 500, because the REST framework didn't know
how to render the response. This fixes the issue.
https://pagure.io/fedora-infrastructure/issue/12134
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
EPEL-10.0 needs an override to use 10 in the repomd URL instead of 10.0.
We'll need to move this forward over time to stay on the leading minor
version, allowing trailing minor versions to use the default repomd URL.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
We don't have a stable repo, so skip the epel-release 'latest' link for
epel10 for now. Since we don't have any modular stuff left, we can just
reuse that conditional. ;)
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
While EPEL 10 will have minor versions, the repo for the leading minor
version will be published as just the major version. This is because it
is intended for use on CentOS Stream 10, which does not indicate a minor
version within the operating system.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
In c7fbc26afe9f770414a49d150d9072c1e58b21ec I switched an integer 41 to
a string, but didn't notice that it was inside another string as part of
the double templating this file does. This results in a template error:
jinja2.exceptions.TemplateSyntaxError: expected token 'end of statement block', got 'integer'
Other strings inside this bigger string use double instead of single
quotes to handle this, so let's take the same approach on this line.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
EPEL 10 has minor versions, and bodhi's Release.version_int property
doesn't handle versions with a dot correctly (yet). Almost all of our
usage is for constructing strings or for equality comparisons that can
be strings, so we can just use Release.version instead. There is an
instance of a numerical greater than or equal to comparison, but it is
inside a condition for release.id_prefix == 'FEDORA', so it shouldn't
get evaluated for EPEL updates.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
This poddler is tracebacking and spewing to logs:
-rw-r--r--. 1 root root 106G Aug 16 00:02 messages.log
Disabling it for now until someone can look at it.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
I had hoped to get some feedback on the message schema, but perhaps the
easiest way is to publish these and figure out if anything is missing or
wrong. We can always update the schema.
Thanks for all the uploads fedimg.
You go to a far far better place I'm sure.
There's no point in keeping it around now, as it's actually not working
and the replacement ( cloud-image-uploader) should work soon.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Now that AWS image uploads work in staging, enable them in production
via the config. A functional build is already deployed to OpenShift in
prod, but since there is no AWS config it won't do anything until we
merge and deploy this.
they cannot work until the first branched compose is done and
mirrormanager is pointing somewhere for f41.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Remove resigning of 41 keys with 42; updated artificats to f41 and rawhide to f42;
updated infra-candidate/openh264 for new f42; f41 signing pending, buildsidetags etc
Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>
