Uploaded image for project: 'CoreOS OCP'
  1. CoreOS OCP
  2. COS-3851 Pipeline monitoring w.s 19012026
  3. COS-3872

build #3015-3019 - GitHub 500 Internal Server Error

XMLWordPrintable

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

      None

      Show
      None
    • False
    • CoreOS East - Sprint 283

      Build Details

      • Job: build
      • Builds #: 3015, 3016, 3017, 3018, 3019
      • Affected Streams: c10s and others
      • Timestamp: 2026-01-22T10:00-10:02 UTC
      • Duration: to 2 minutes each

      Affected Builds

      Build # Stream Duration
      3015 c10s 2 min
      3016 (unknown) min
      3017 (unknown) min
      3018 (unknown) min
      3019 (unknown) min

      Root Cause

      GitHub experienced a transient outage returning HTTP 500 Internal Server Errors around 10:00-10:02 UTC, preventing the builds from cloning required repositories.

      Error Messages

      # Build 3015 (c10s)
      git clone --branch=main https://github.com/coreos/rhel-coreos-config config
      remote: Internal Server Error
      fatal: unable to access 'https://github.com/coreos/rhel-coreos-config/': The requested URL returned error: 500
      
      # Builds 3016-3019
      git fetch --tags --force --progress -- https://github.com/coreos/fedora-coreos-pipeline
      remote: Internal Server Error
      fatal: unable to access 'https://github.com/coreos/fedora-coreos-pipeline/': The requested URL returned error: 500
      

      Additional Issue (Build 3015)

      Pod launch failures for ~2 minutes before the build could start:

      ERROR: Failed to launch pod-8dd39a32-ae87-49f5-9ce2-b8ef024788c3-lzg8t-zb7jr
      ... (11 more pod launch failures)
      

      Resolution

      • c10s Retry Build #: 3020
      • Retry Result: In progress / Success
      • Action: Transient GitHub outage, no action required

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

                Created:
                Updated:
                Resolved: