I'm running a private Koji instance (have been for a while) and have started
to see that newRepo/createRepo tasks are writing out repos with the wrong
permissions on files or directories, which leads to failures:
OSError: [Errno 13] Permission denied: '/mnt/koji/repos/f26-build/9294'
drwx------. 4 apache apache 4096 Aug 24 17:45 9291
drwx------. 4 apache apache 4096 Aug 24 17:45 9292
drwxr-xr-x. 4 apache apache 4096 Aug 24 17:48 9293
drwx------. 4 apache apache 4096 Aug 24 17:48 9294
My Koji hub and builders are fully updated F26 x86_64 machines. Has anyone
seen this? Andy pointers on where to start debugging this issue?
Thanks in advance. -A
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6
I forgot to notify this mailing list - last week I released new version of Mock:
From release notes:
Released on 2017-09-15.
This is mostly a bugfix release, but there are some features too:
* All chroot configs have been moved to new package mock-base-configs. This will allow us to release new chroot
configs independently of Mock main code.
* There is a new command --debug-config available. This command print current mock config (including defaults) to
standard output and exit. This can be useful when you experience some issue, which you cannot reproduce anywhere else.
* There is a new script, which can add a default route to loopback for a container with private-network. This is an
experimental feature, not used automatically, and will very likely change in future.
* There is short option -N for --no-cleanup-after.
* Mock again create /dev/loop nodes. This caused a lot of pain to Lorax users. RHBZ#1481370
* Comment about nspawn/chroot default in site-defaults.cfg was previously incorrect, this has been fixed now.
* Previously when you used --private-network then the isolated network was used only during rpm build phase. And,
e.g., for shell command, it was not used. This caused some confusion. Now the network is always switched when you
* The bug "The buildroot LVM volume is not kept mounted after build" RHBZ#1447658 has been fixed once again.
Hopefully this time correctly.
Following contributors contributed to this release:
Brian C. Lane
P.S. I did not skip 1.4.5. I just find a serious bug in requirement just after the release. So I made two releases in
one day. :) This is united release notes.
I have a couple of private Koji instances I maintain that have the
Fedora repositories added as an external source via local mirrors.
When a Fedora releases reaches EoL, I follow along and to reduce disk
usage of the mirrors, I will delete the older releases. Recently F24
went this route but kojira still tries to run newRepo tasks against my
f24-build tag and fails because the mirror is gone. How can I stop
kojira for these older releases? I've tried lock-tag, but that didn't
seem to make any difference.
What is the easiest way to log some data from my mock.cfg / site-defaults.cfg ?
I dynamically load repo-priority file and generates repos-data. So I want to print some
debug as INFO message. How can I connect to mock's logger, so I wouldn't see my debug with
mock -q -r ...
and would see it otherwise (without -q) ?
I take a look into sources and find there is logging.warning level before reading config files..=\
I would like to split mock package into two separate packages: mock and mock-config. I mean even sources, so we will
have two src.rpm packages.
Mock-config will have all chroot configs. Basically anything in /etc/mock* but site-defaults.cfg.
This change will allow immediate update of configs when Fedora is branched.