Learn more about these different git repos.
Other Git URLs
Describe the issue It seems that all EPEL8 and ELN module builds are failing at this moment. EPEL8 fails immediately, ELN seems to time out building module-build-macros.
module-build-macros
When do you need this? (YYYY/MM/DD) When convenient.
When is this no longer needed or useful? (YYYY/MM/DD) 2029 (RHEL8 EOL).
If we cannot complete your request, what is the impact? No more modules for EPEL8 can be built.
CC: @breilly
Metadata Update from @kevin: - Issue tagged with: medium-gain, medium-trouble
Do you have an example for the EPEL8 failures?
I see a recent failed ELN build, as you say it times out, during the wait repo specifically: https://release-engineering.github.io/mbs-ui/module/14762/components https://koji.fedoraproject.org/koji/taskinfo?taskID=89783434 @kevin any known issue with koji's createrepo channel, or kojira, at the moment that could cause this?
We have a mass rebuild running right now, so koji is pretty busy, but kojira should be running and processing as normal...
ELN builds are failing because F34 was EOL-ed and module-eln-build Koji tag still refers to f34-build external repo:
module-eln-build
f34-build
$ koji taginfo module-eln-build Tag: module-eln-build [31229] Arches: Groups: Tag options: External repos: 5 f34-build (https://kojipkgs.fedoraproject.org/repos/f34-build/latest/$arch/, merge mode: koji), arches: inherited from tag Inheritance: 0 .... module-package-list [412]
Koji can't create modular buildroots because external repo f34-build is no longer available.
Here are the latest 3 EL8 builds that failed: https://release-engineering.github.io/mbs-ui/module/14769 https://release-engineering.github.io/mbs-ui/module/14759 https://release-engineering.github.io/mbs-ui/module/14753
They failed due to:
An unknown error occurred while validating the modulemd
EL8 failures are caused by a different issue that ELN failures. I've fixed an issue in MBS (incorrect filesystem permissions on mbs-backend), please retry your failed EL8 module build(s).
@mizdebsk what permission was it? can we/should we add it to ansible?
On mbs-backend01 some (but not all) files under /tmp/mbs/dnf/module-el8-build-37/ directory were owned by root:root instead of fedmsg:fedmsg. I don't know how that happened. These files are not ansible-managed, so there is nothing to fix in ansible. I removed the whole directory manually and let MBS recreate it - now it has correct ownership.
mbs-backend01
/tmp/mbs/dnf/module-el8-build-37/
This issue seems to be resolved, if the problems persist please reopen this ticket.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.