Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-80260

podman artifact pull: --retry-delay values are ignored - RHEL 10.0 GA 0day

XMLWordPrintable

    • No
    • Moderate
    • rhel-sst-container-tools
    • 1
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Requested
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • All
    • None

      On the RUN board at https://issues.redhat.com/browse/RUN-2511:

      Yuhui Jiang from QE reports that the value for --retry-delay on podman artifact pull is ignored.  The retries are in fact done but the interval is always the default value (1 sec).

      [root@kvm-01-guest14 ~]# podman artifact pull  --retry 2 --retry-delay 30 -q 127.0.0.1/testimage
WARN[0000] Failed, retrying in 1s ... (1/2). Error: initializing source docker://127.0.0.1/testimage:latest: pinging container registry 127.0.0.1: Get "https://127.0.0.1/v2/": dial tcp 127.0.0.1:443: connect: connection refused
WARN[0001] Failed, retrying in 1s ... (2/2). Error: initializing source docker://127.0.0.1/testimage:latest: pinging container registry 127.0.0.1: Get "https://127.0.0.1/v2/": dial tcp 127.0.0.1:443: connect: connection refused
Error: initializing source docker://127.0.0.1/testimage:latest: pinging container registry 127.0.0.1: Get "https://127.0.0.1/v2/": dial tcp 127.0.0.1:443: connect: connection refused

       

              bbaude@redhat.com Brent Baude
              tsweeney@redhat.com Tom Sweeney
              Container Runtime Eng Bot Container Runtime Eng Bot
              Yuhui Jiang Yuhui Jiang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: