fedora-infrastructure

#7564 s390x builders fail from time to time
Closed: Fixed by kevin. Opened by ignatenkobrain.

Closed: Fixed
Reopen Issue

https://koji.fedoraproject.org/koji/taskinfo?taskID=32756421

DEBUG util.py:579:  Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', 'c2849834522444b2a29c4634edc583cb', '-D', '/var/lib/mock/module-bat-latest-2920190212081617-7fdbb362-build-15234086-1090376/root', '-a', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--setenv=LD_PRELOAD=/var/tmp/tmp.mock.8hs81vpo/$LIB/nosync.so', '/usr/sbin/userdel', '-r', '-f', 'mockbuild'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'LD_PRELOAD': '/var/tmp/tmp.mock.8hs81vpo/$LIB/nosync.so'} and shell False
DEBUG util.py:325:  Unsharing. Flags: 134217728
DEBUG util.py:490:  BUILDSTDERR: Failed to register machine: Connection timed out

Because of this, all my rust modules fail to build (because one of components always get to such builder).

Same here: https://koji.fedoraproject.org/koji/taskinfo?taskID=32795921

That was different builder.

And this:
https://koji.fedoraproject.org/koji/taskinfo?taskID=32807847

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/koji/daemon.py", line 1244, in runTask
    response = (handler.run(),)
  File "/usr/lib/python2.7/site-packages/koji/tasks.py", line 307, in run
    return koji.util.call_with_argcheck(self.handler, self.params, self.opts)
  File "/usr/lib/python2.7/site-packages/koji/util.py", line 216, in call_with_argcheck
    return fu ...

Metadata Update from @bowlofeggs:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: koji

I made some changes early today UTC to our varnish config.

Have things been better today?

There is one outstanding issue I want to fix: The varnish cache there is supposed to use kojipkgs01 and kojipkgs02 as origins, but due to firewall rules, 02 is not accessable, so it's only using kojipkgs01. I have a ticket in to fix the firewalling there. I am hoping that between the timeout changes and adding another backend, we will be in much better shape.

ok, the second backend is now working.

I'm monitoring for 503's and if any of you could re-open this if you hit this again that would be great.

Finger crossed that this fixes things.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None

koji

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.