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

The MCD can exit(255) during an upgrade and and degrade on content mismatch


    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 4.16.0
    • 4.16.0
    • None
    • Critical
    • None
    • Proposed
    • False
    • Hide


    • Release Note Not Required
    • In Progress

      Description of problem

      Spin off of OCPBUGS-30192

      The daemon process can exit due to health check failures in 4.16+, after we added apiserver server CA rotation handling. The came with the side effect that if the MCD happens to exit in the middle of the update (e.g. image pull portion), the files/units would have been updated but the OS upgrade would not, blocking the upgrade indefinitely when the new container comes up.

      Version-Release number of selected component


      How reproducible

      Only in BM CI so far, unsure if other issues contribute to this.

      Steps to Reproduce

      Get lucky and have api-int DNS break while the machine-config daemon is deploying updated files to disk. Unclear how to reliably trigger this, or distinguish from OCPBUGS-30192 and other failure modes.

      Actual results

      Expected results

      Additional info

            trking W. Trevor King
            jerzhang@redhat.com Yu Qi Zhang
            Sergio Regidor de la Rosa Sergio Regidor de la Rosa
            0 Vote for this issue
            14 Start watching this issue