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

Pod Termination During Checkpoint with TCP-CLOSED Socket in OpenShift

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 4.14, 4.16
    • Node / CRI-O
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      Checkpointing a pod in OpenShift fails when it has TCP sockets in the TCP-CLOSED state, causing the pod to terminate unexpectedly.


      Steps to Reproduce

      1. Deploy a pod with an app that opens and closes a TCP connection.
      1. Wait until the socket enters the TCP-CLOSED state.
      1. Run criu dump or trigger OpenShift checkpoint.
      1. Observe the pod is terminated.

      Expected Behavior

      Pod should remain running. TCP-CLOSED sockets should be handled gracefully during checkpoint.


      Actual Behavior

      Pod is terminated during checkpoint due to unhandled TCP-CLOSED socket state.


      Impact

      Blocks live migration, debugging, and resilience features relying on checkpoint/restore.

              areber@redhat.com Adrian Reber
              ashaikev Assaf Shaikevich
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: