On Tue, Aug 31, 2021 at 9:41 AM Richard W.M. Jones <rjones(a)redhat.com> wrote:
On Tue, Aug 31, 2021 at 10:29:27AM -0400, Neal Gompa wrote:
> On Tue, Aug 31, 2021 at 10:13 AM Daniel P. Berrangé <berrange(a)redhat.com>
wrote:
> >
> > On Tue, Aug 31, 2021 at 10:07:38AM +0100, Richard W.M. Jones wrote:
> > >
> > >
https://koji.fedoraproject.org/koji/taskinfo?taskID=74840901
> > >
> > > How should I interpret this?
> >
> > Very odd
> >
> > Looking at the parent task:
> >
> >
https://koji.fedoraproject.org/koji/taskinfo?taskID=74840893
> >
> > and picking ppc64 arch instead, it gets even wierder. The root.log file:
> >
> >
https://kojipkgs.fedoraproject.org//work/tasks/903/74840903/root.log
> >
> >
> > contains strace logs:
> >
> > DEBUG util.py:446: execve("/bin/kernel-install",
["/bin/kernel-install", "-v", "add",
"5.14.0-61.fc36.ppc64le",
"/lib/modules/5.14.0-61.fc36.ppc64le/vmlinuz"], 0x7fffc420e508 /* 12 vars */) =
0
> > DEBUG util.py:446: brk(NULL) = 0x13c870000
> > DEBUG util.py:446: readlink("/proc/self/exe",
"/usr/bin/bash", 4096) = 13
> > DEBUG util.py:446: openat(AT_FDCWD,
"/var/tmp/tmp.mock.gzh1qs1v/lib64/nosync.so", O_RDONLY|O_CLOEXEC) = 3
> > ...snip...
> >
> >
> > What on earth is going on there ?
> >
> > Who would be running strace on a *production* build system host ?
> >
>
> Apparently us:
https://src.fedoraproject.org/rpms/kernel/c/6b7647647610ebe404bd27c768e5d...
Is this related to the OOM issues in Koji, or something else?
(In fact now I ask that question I wonder if this could somehow be
_causing_ the OOM issues ...)
No, this was added to one build at the request of releng because
composes are randomly failing in kernel-core %post. As we just call
kernel-install, we first tried calling kernel-install -v, but that
doesn't give much useful information because it doesn't seem to add
any verbosity to the subtasks it runs. The 5.14.0-61 build was done
last night to try and gather some more information for them, and the
strace call is expected to disappear with the next build. In fact,
once they have run the composes and gotten the information needed, 61
can be untagged, and 60 will be the same kernel without the debugging
calls to kernel-install. It should only impact the very few packages
which have kernel-core as a buildreq.
Justin