Pavel Raiskup
Pavel Raiskup
In procyon package, there's [ExclusiveArch: %{java_arches} noarch](https://src.fedoraproject.org/rpms/procyon/blob/rawhide/f/procyon.spec#_23). This expands on my host like: ``` $ rpm --eval "%java_arches noarch" aarch64 ppc64le s390x x86_64 noarch ``` So it really appears to...
Hm, Koji seems to handle procyon builds just fine on ppc64le: https://koji.fedoraproject.org/koji/buildinfo?buildID=2226538
This must be a different bug then. Let's resolve this post-release.
Note for myself: Reproducible on Power8.
Hmm is this so old https://bugzilla.redhat.com/show_bug.cgi?id=1461288 ??
Thank you for the traceback, I did this work-around then: ```patch --- /usr/lib/python3.12/site-packages/resallocserver/manager.py 2024-03-15 00:00:00.000000000 +0000 +++ /usr/lib/python3.12/site-packages/resallocserver/manager.py 2024-04-04 08:02:46.355468553 +0000 @@ -643,8 +643,8 @@ normalize_tags(obj) if self.tags_on_demand and self.max_prealloc...
We should use a separate log file for webserver vs. resalloc manager.
Deployed on both Fedora Copr and Red Hat Copr.
Triage time: @xsuchy proposes a cache invalidation
If not configurable, I believe we could at least have a better default - like 3 months for failed logs (as long as the build driectory with logs is