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

MCO the content mismatch bug revised when upgrading from 4.13.23 to 4.14.3

    XMLWordPrintable

Details

    • No
    • MCO Sprint 247
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the Machine Config Operator allowed user-provided certificate authority updates to be made without requiring a new machine config to trigger. Because the new write method for these updates was missing a newline character, it caused validation errors for the contents of the CA file on-disk and the Machine Config Daemon became degraded. With this release, the CA file contents are fixed, and updates proceed as expected. (link:https://issues.redhat.com/browse/OCPBUGS-25424[*OCPBUGS-25424*])
      Show
      * Previously, the Machine Config Operator allowed user-provided certificate authority updates to be made without requiring a new machine config to trigger. Because the new write method for these updates was missing a newline character, it caused validation errors for the contents of the CA file on-disk and the Machine Config Daemon became degraded. With this release, the CA file contents are fixed, and updates proceed as expected. (link: https://issues.redhat.com/browse/OCPBUGS-25424 [* OCPBUGS-25424 *])
    • Bug Fix
    • Done

    Description

      This is a clone of issue OCPBUGS-25245. The following is the description of the original issue:

      Description of problem:

          When upgrading cluster from 4.13.23 to 4.14.3, machine-config CO gets stuck due to a content mismatch error on all nodes.
      
      Node node-xxx-xxx is reporting: "unexpected on-disk state
            validating against rendered-master-734521b50f69a1602a3a657419ed4971: content
            mismatch for file \"/etc/pki/ca-trust/source/anchors/openshift-config-user-ca-bundle.crt\""

      Version-Release number of selected component (if applicable):

          

      How reproducible:

          always

      Steps to Reproduce:

          1. perform a upgrade from 4.13.x to 4.14.x
          2. 
          3.
          

      Actual results:

          machine-config stalls during upgrade

      Expected results:

          the "content mismatch" shouldn't happen anymore according to the MCO engineering team

      Additional info:

          

      Attachments

        Issue Links

          Activity

            People

              cdoern@redhat.com Charlie Doern
              openshift-crt-jira-prow OpenShift Prow Bot
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: