Issue #246: Zuul is down (CI builds fail) - general

fedora-ci / general

#246 Zuul is down (CI builds fail)

Closed 3 years ago by fbo. Opened 3 years ago by ksurma.

Zuul, as a part of our CI in Fedora dist-git, has just started failing builds, see this or this job.

check-for-arches fails says:

The conditional check 'check_for_arches_ignore or tests_noarch.stdout_lines != []' failed. The error was: error while evaluating conditional (check_for_arches_ignore or tests_noarch.stdout_lines != []): 'dict object' has no attribute 'stdout_lines'

The error appears to be in '/var/lib/zuul/builds/420d909ec905409987e240632f5d7a6b/trusted/project_3/pagure.io/fedora-zuul-jobs-config/playbooks/rpm/check-for-arches.yaml': line 16, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:
    - zuul_return:
      ^ here

rpm-scratch-build fails with:

Traceback (most recent call last):
  File "<stdin>", line 102, in <module>
  File "<stdin>", line 94, in _ansiballz_main
  File "<stdin>", line 40, in invoke_module
  File "/usr/lib64/python3.9/runpy.py", line 210, in run_module
    return _run_module_code(code, init_globals, run_name, mod_spec)
  File "/usr/lib64/python3.9/runpy.py", line 97, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "/usr/lib64/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/tmp/ansible_command_payload_2lr4q65t/ansible_command_payload.zip/ansible/modules/command.py", line 675, in <module>
  File "/tmp/ansible_command_payload_2lr4q65t/ansible_command_payload.zip/ansible/modules/command.py", line 620, in main
FileNotFoundError: [Errno 2] No such file or directory: '/root/src/src.fedoraproject.org/rpms/python-pip'
Error: non zero exit code: 1: OCI runtime error
error:

Metadata Update from @fbo:
- Issue tagged with: Zuul CI

3 years ago

fbo commented 3 years ago

Thanks you for the report. A recent change in our container images in order to make them compatible with OpenShift introduced an issue with our current container manager. We are investigating the issue.