Uploaded image for project: 'CoreOS OCP'
  1. CoreOS OCP
  2. COS-3915 Pipeline monitoring w.s 23022026
  3. COS-3976

build-node-image #2695: 4.21-9.6 failed with registry EOF errors

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • CoreOS East - Sprint 284

      Summary

      Build-node-image #2695 for 4.21-9.6 failed due to transient network/registry connectivity issues.

      Error Details

      Two podman commands failed with EOF errors:

      1. Podman push (x86_64):
        Error: failed to decode message from stream: unexpected EOF
        Command: podman push registry.ci.openshift.org/coreos/node-staging:4.21-9.6-node-image-x86_64
        
      1. Podman build (aarch64):
        Error: server probably quit: unexpected EOF
        Command: podman build ... --tag=registry.ci.openshift.org/coreos/node-staging:4.21-9.6-node-image-aarch64
        

      Analysis

      This is a transient infrastructure flake - network connectivity issues to registry.ci.openshift.org.

      Evidence:
      - Build #2693 succeeded immediately before
      - 12+ consecutive successes preceded this failure
      - Most build steps completed successfully before the registry communication failed

      Jenkins Link

      https://jenkins-rhcos--prod-pipeline.apps.int.prod-stable-spoke1-dc-iad2.itup.redhat.com/job/build-node-image/2695/

              Unassigned Unassigned
              cverna@redhat.com Clément Verna
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: