Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-16715

community-e2e-images missing manifest listed images

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Normal
    • 4.14.0
    • 4.14
    • Multi-Arch
    • None
    • No
    • Multi-Arch Sprint 239, Multi-Arch Sprint 240, Multi-Arch Sprint 241, Multi-Arch Sprint 242
    • 4
    • Rejected
    • x86_64, aarch64, ppc64le, s390x
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:
      Ben ran an update to pull the upstream images and push some updates to quay.io. Somehow, we ended up in a state where these 6 images were push but a single-arch x86 images:

      docker.io/library/registry:2.8.0-beta.1 quay.io/openshift/community-e2e-images:e2e-docker-io-library-registry-2-8-0-beta-1-8x_YFKSuz9Xw6lZD
quay.io/openshifttest/ldap:1.2 quay.io/openshift/community-e2e-images:e2e-quay-io-openshifttest-ldap-1-2-O3f5zPgtmWzEtasv
quay.io/openshifttest/multicast:1.1 quay.io/openshift/community-e2e-images:e2e-quay-io-openshifttest-multicast-1-1-XSI8Fm3bAh556UCx
quay.io/redhat-developer/nfs-server:1.1 quay.io/openshift/community-e2e-images:e2e-quay-io-redhat-developer-nfs-server-1-1-dlXGfzrk5aNo8EjC
quay.io/redhat-developer/test-build-roots2i:1.2 quay.io/openshift/community-e2e-images:e2e-quay-io-redhat-developer-test-build-roots2i-1-2-gLJ7WcnS2TSllJ32
quay.io/redhat-developer/test-build-simples2i:1.2 quay.io/openshift/community-e2e-images:e2e-quay-io-redhat-developer-test-build-simples2i-1-2-thirLMR-JKplfkmE

      How reproducible:

      openshift-tests images --upstream --to-repository=quay.io/jpoulin/community-e2e-images | grep openshift/community-e2e-images

      Steps to Reproduce:

      TBD

      Actual results:

      Subset of synced images invalid.

      Expected results:

      All images in quay.io/openshift/community-e2e-images to be an exactly replica of the upstream images

      Additional info:

      Current the immediate break is resolved. We resolved it by making a file with just the images above listed and rerunning the sync command on only those images.

      Attachments

        1. image-scan.sh
          0.7 kB
        2. release-4.10.txt
          45 kB
        3. release-4.11.txt
          10 kB
        4. release-4.12.txt
          10 kB
        5. release-4.13.txt
          10 kB
        6. release-4.14.txt
          11 kB

        Issue Links

          is depended on by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-15573 4.14 Regressions in periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-remote-libvirt-ppc64le - Node Enters NotReady State

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-16619 4.14 Regressions in periodic-ci-openshift-multiarch-master-nightly-4.14-ocp-e2e-ovn-remote-libvirt-s390x - TLS Handshake Timeout

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MULTIARCH-3746 CI should detect when images fall out of sync

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • To Do

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MULTIARCH-3747 CI should auto-sync images when out of sync

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • To Do

          Activity

            People

              jpoulin Jeremy Poulin
              jpoulin Jeremy Poulin
              Doug Slavens Doug Slavens
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: