Uploaded image for project: 'Container Tools'
  1. Container Tools
  2. RUN-2212

[containers/podman] race: completion: Top layer ... not found ... storage may be corrupted

XMLWordPrintable

    • 5
    • False
    • None
    • False
    • rhel-sst-container-tools
    • RUN 258

      [2417260209] Upstream Reporter: Ed Santiago
      Upstream issue status: Closed
      Upstream description:

      Another parallel-system-test flake in command completion, seen in f39 rootless:

      <+048ms> # $ podman __completeNoDesc  image tag
      <+097ms> # [Debug] 2 arg(s), received 1
               # time="2024-07-18T12:56:33-05:00" level=warning msg="Top layer f6adb48d9895082456c5aa8074e44f3d32852702f03d54110bb34f01bb8821c0 of image 5fd625cf9c7cb8392d7acb93aac1276dd4fcb0c06ebb891485d01384f99932dc not found in layer tree. The storage may be corrupted, consider running `podman system reset`."
               # localhost/i_t109-kniryp3x:58ibj
               # quay.io/libpod/testimage:20240123
               # localhost/podman-pause:5.2.0-dev-1721323759
               # quay.io/libpod/systemd-image:20240124
               # :4
               # Completion ended with directive: ShellCompDirectiveNoFileComp
               # #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
               # #| FAIL: Command succeeded, but issued unexpected warnings
               # #^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

      I haven't tried to look for a reproducer yet.


      Upstream URL: https://github.com/containers/podman/issues/23331

              jrodak Jan Rodák
              upstream-sync Upstream Sync
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: