Bug 2142731 - containerbuilds failing: Not Found ("lstat /usr/lib/sysimage/rpm: no such file or directory")}. OSBS build id: fedora-toolbox-f37-65bbb-3'>
Summary: containerbuilds failing: Not Found ("lstat /usr/lib/sysimage/rpm: no such fil...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: atomic-reactor
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-15 05:46 UTC by Jens Petersen
Modified: 2023-11-23 08:36 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-23 08:36:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jens Petersen 2022-11-15 05:46:17 UTC
Description of problem:
As reported also in https://github.com/containerbuildsystem/atomic-reactor/issues/2027 containerbuilds are failing koji OSBS for F36+

Initially reported to https://pagure.io/releng/issue/11092

Version-Release number of selected component (if applicable):
atomic-reactor-3.14.0-1

How reproducible:
100%

Steps to Reproduce:
1. Try to build fedora-toolbox:37 (or 36 or 38) in the fedora buildsystem

Actual results:
2022-11-08 12:03:50,962 - atomic_reactor.plugin - DEBUG - plugin 'remove_built_image' finished in 0s
2022-11-08 12:03:51,014 - atomic_reactor.inner - INFO - Dockerfile used for build:
FROM registry.fedoraproject.org/fedora:38

ENV NAME=fedora-toolbox VERSION=38
LABEL com.github.containers.toolbox="true" \
      com.github.debarshiray.toolbox="true" \
      com.redhat.component="$NAME" \
      name="$NAME" \
      version="$VERSION" \
      usage="This image is meant to be used with the toolbox command" \
      summary="Base image for creating Fedora toolbox containers" \
      maintainer="Debarshi Ray <rishi>"

COPY README.md /

RUN sed -i '/tsflags=nodocs/d' /etc/dnf/dnf.conf
RUN dnf -y swap coreutils-single coreutils-full

COPY missing-docs /
RUN dnf -y reinstall $(<missing-docs)
RUN rm /missing-docs

COPY extra-packages /
RUN dnf -y install $(<extra-packages)
RUN rm /extra-packages

RUN dnf clean all

LABEL "release"="2" "authoritative-source-url"="registry.fedoraproject.org" "distribution-scope"="public" "vendor"="Fedora Project" "build-date"="2022-11-08T12:02:12.919528" "architecture"="x86_64" "vcs-type"="git" "vcs-ref"="32bf967e6d08cc406c56758ee037ed4fb3b978a5" "com.redhat.build-host"="osbs-node02.iad2.fedoraproject.org"

2022-11-08 12:03:51,014 - atomic_reactor.inner - ERROR - image build failed: plugin 'all_rpm_packages' raised an exception: RuntimeError: 404 Client Error for http+docker://localhost/v1.26/containers/3d3e6847d772287201af8cbd7549a7120385e46b1abda1092d874427ce90df59/archive?path=%2Fvar%2Flib%2Frpm: Not Found ("lstat /usr/lib/sysimage/rpm: no such file or directory")
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/docker/api/client.py", line 268, in _raise_for_status
    response.raise_for_status()
  File "/usr/lib/python3.10/site-packages/requests/models.py", line 960, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.26/containers/3d3e6847d772287201af8cbd7549a7120385e46b1abda1092d874427ce90df59/archive?path=%2Fvar%2Flib%2Frpm

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/atomic_reactor/plugins/post_rpmqa.py", line 72, in gather_output
    bits, _ = self.tasker.get_archive(container_id, RPMDB_PATH)
  File "/usr/lib/python3.10/site-packages/atomic_reactor/core.py", line 375, in get_archive
    return self.tasker.get_archive(*args, **kwargs)
  File "/usr/lib/python3.10/site-packages/atomic_reactor/core.py", line 961, in get_archive
    return self.d.get_archive(container_id, dir_path)
  File "/usr/lib/python3.10/site-packages/atomic_reactor/core.py", line 243, in hooked
    return retry(orig_attr, *args, retry=self.retry_times, **kwargs)
  File "/usr/lib/python3.10/site-packages/atomic_reactor/core.py", line 210, in retry
    return function(*args, **kwargs)
  File "/usr/lib/python3.10/site-packages/docker/utils/decorators.py", line 19, in wrapped
    return f(self, resource_id, *args, **kwargs)
  File "/usr/lib/python3.10/site-packages/docker/api/container.py", line 748, in get_archive
    self._raise_for_status(res)
  File "/usr/lib/python3.10/site-packages/docker/api/client.py", line 270, in _raise_for_status
    raise create_api_error_from_http_exception(e)
  File "/usr/lib/python3.10/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
    raise cls(e, response=response, explanation=explanation)
docker.errors.NotFound: 404 Client Error for http+docker://localhost/v1.26/containers/3d3e6847d772287201af8cbd7549a7120385e46b1abda1092d874427ce90df59/archive?path=%2Fvar%2Flib%2Frpm: Not Found ("lstat /usr/lib/sysimage/rpm: no such file or directory")

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/atomic_reactor/plugin.py", line 265, in run
    plugin_response = plugin_instance.run()
  File "/usr/lib/python3.10/site-packages/atomic_reactor/plugins/post_rpmqa.py", line 47, in run
    plugin_output = self.gather_output()
  File "/usr/lib/python3.10/site-packages/atomic_reactor/plugins/post_rpmqa.py", line 77, in gather_output
    raise RuntimeError(ex) from ex
RuntimeError: 404 Client Error for http+docker://localhost/v1.26/containers/3d3e6847d772287201af8cbd7549a7120385e46b1abda1092d874427ce90df59/archive?path=%2Fvar%2Flib%2Frpm: Not Found ("lstat /usr/lib/sysimage/rpm: no such file or directory")

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/bin/atomic-reactor", line 33, in <module>
    sys.exit(load_entry_point('atomic-reactor==3.14.0', 'console_scripts', 'atomic-reactor')())
  File "/usr/lib/python3.10/site-packages/atomic_reactor/cli/main.py", line 315, in run
    cli.run()
  File "/usr/lib/python3.10/site-packages/atomic_reactor/cli/main.py", line 297, in run
    args.func(args)
  File "/usr/lib/python3.10/site-packages/atomic_reactor/cli/main.py", line 95, in cli_inside_build
    build_inside(input_method=args.input, input_args=args.input_arg,
  File "/usr/lib/python3.10/site-packages/atomic_reactor/inner.py", line 619, in build_inside
    build_result = dbw.build_docker_image()
  File "/usr/lib/python3.10/site-packages/atomic_reactor/inner.py", line 545, in build_docker_image
    postbuild_runner.run()
  File "/usr/lib/python3.10/site-packages/atomic_reactor/plugin.py", line 306, in run
    raise PluginFailedException(msg) from ex
atomic_reactor.plugin.PluginFailedException: plugin 'all_rpm_packages' raised an exception: RuntimeError: 404 Client Error for http+docker://localhost/v1.26/containers/3d3e6847d772287201af8cbd7549a7120385e46b1abda1092d874427ce90df59/archive?path=%2Fvar%2Flib%2Frpm: Not Found ("lstat /usr/lib/sysimage/rpm: no such file or directory")

Expected results:
No error like on aarch64.

Additional info:
According to the rel-eng ticket the rpmqa.py isn't being used on aarch64 for some reason, which is why aarch64 doesn't fail.

This is preventing updating the fedora-toolbox:37 image to GA - the current out of date container image from the Beta timeframe, still has updates-testing enabled. :-(

A simple workaround seems to be just patching the rpmdb dir path to the new location for F36+, until it gets fixed upstream.

Comment 1 Jens Petersen 2022-11-15 12:04:28 UTC
I opened https://src.fedoraproject.org/rpms/atomic-reactor/pull-request/12

Comment 2 Aoife Moloney 2023-11-23 00:30:51 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.


Note You need to log in before you can comment on or make changes to this bug.