Uploaded image for project: 'CoreOS OCP'
  1. CoreOS OCP
  2. COS-3131

[coreos/fedora-coreos-tracker] kola iscsi tests fail intermittently because of 502 error when pulling container

XMLWordPrintable

    • Upstream
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Integration & Delivery - 266
    • 0
    • 0.000

      [2810398634] Upstream Reporter: Dusty Mabe
      Upstream issue status: Closed
      Upstream description:

      For example the `iso-offline-install-iscsi.ibft-with-mpath.bios` will fail without much info on what happened. If you look at the `nested_vm_console.txt` you'll see:

      ```
      Trying to pull quay.io/coreos-assembler/coreos-assembler:latest...
      Pulling image //quay.io/coreos-assembler/coreos-assembler:latest inside systemd: setting pull timeout to 5m0s
      Error: copying system image from manifest list: determining manifest MIME type for docker://quay.io/coreos-assembler/coreos-assembler:latest: reading manifest sha256:9d5c60213547ca29dda408ed4b26313d0d5ff390b9beb0cbdfdc2d6866b33eb9 in quay.io/coreos-assembler/coreos-assembler: received unexpected HTTP status: 502 Bad Gateway
      ```

      This is coming from [this unit](https://github.com/coreos/coreos-assembler/blob/7dd4b4d388ba533275f9e9815ba0bbcaa4c7d0db/mantle/cmd/kola/resources/iscsi_butane_setup.yaml#L93-L117)

      I think this is fundamentally a problem we need to get fixed with podman to retry 500 errors - see https://github.com/containers/common/issues/2299

              rhn-gps-dmabe Dusty Mabe
              upstream-sync Upstream Sync
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: