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

pause_image content mismatch for file "/etc/crio/crio.conf.d/00-default"

XMLWordPrintable

    • Important
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Upgrade from 4.16.14 to 4.16.15 stuck for control plane node due to following error in machine-config-daemon logs:

      E1013 06:55:23.406306 3660133 on_disk_validation.go:251] content mismatch for file "/etc/crio/crio.conf.d/00-default" (-want +got):
        []uint8(
              """
              ... // 53 identical lines
              [crio.image]
              global_auth_file = "/var/lib/kubelet/config.json"
      -       pause_image = "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:4fda2303083e894e928ee6bfb05822fed6d6e713bc174b89e9ba2aee2c3a58b9"
      +       pause_image = "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ba31899a50e873490efd06395669cc067907b9efc9f7728b1132d44941c4046c"
              pause_image_auth_file = "/var/lib/kubelet/config.json"
              pause_command = "/usr/bin/pod"
              ... // 39 identical lines
              """
        )
      E1013 06:55:23.406473 3660133 daemon.go:931] Preflight config drift check failed: unexpected on-disk state validating against rendered-master-2c81e066ae7fdcc49b0a2884c5aab784: content mismatch for file "/etc/crio/crio.conf.d/00-default"
      E1013 06:55:23.406517 3660133 writer.go:226] Marking Degraded due to: unexpected on-disk state validating against rendered-master-2c81e066ae7fdcc49b0a2884c5aab784: content mismatch for file "/etc/crio/crio.conf.d/00-default"
      I1013 06:56:23.703623 3660133 rpm-ostree.go:308] Running captured: rpm-ostree kargs
      E1013 06:56:23.704653 3660133 daemon.go:931] Preflight config drift check failed: unexpected on-disk state validating against rendered-master-2c81e066ae7fdcc49b0a2884c5aab784: error running rpm-ostree kargs: signal: killed    

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

      4.16.14 -> 4.16.15    

      Steps to Reproduce:

          1. Perform upgrade from 4.16.14 to 4.16.15
          2. Wait for control plane upgrade to start
          

      Actual results:

      Upgrade stuck in control plane upgrade    

      Expected results:

      Upgrade not stuck    

      Additional info:

      Cluster is Managed OpenShift cluster on AWS (ROSA)    

              team-mco Team MCO
              travi.openshift Ravi Trivedi
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: