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

MCP stuck due to issue with OSimagetarget

XMLWordPrintable

    • Critical
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Cluster upgrade is stuck and not progressing due to mismatch of OSimageURL,

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

          4.12

      How reproducible:

          We do not have steps to reproduce

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

      Upgrade stuck    

      Expected results:

          upgrade to complete smooth

      Additional info:

       node is rebooted multiple times, The desired and current config is the same, The OSimage url is the same in the oc get node -o yaml
      
      rpm-ostree status 
      State: idle 
      Deployments: 
      ● pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:342776e7a08f5ffc3d932e51f0135bd39d0867a98df1dd9f4d224ac941664941 CustomOrigin: Managed by machine-config-operator Version: 411.86.202308170928-0 (2023-08-17T09:32:02Z)
      
      Tried rebase
      rpm-ostree rebase --experimental ostree-unverified-registry:quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ee58e881ff6aed01b506e6d7564b7f8c23734a498a499b586631830f06f08d9b
      
      Error with rebase
      
      error: Parsing layer blob sha256:0e7f9ee49071d8feb8d6a0d3ebd762e89e21f10c2e9b57f5ebc70b67c20435c9: Failed to commit tar: ExitStatus(unix_wait_status(256)): error: ostree-tar: Processing deferred hardlink sysroot/ostree/repo/objects/47/232577c37499690f945544cc477ad728882738877d45b741089fc46ae121c0.file: Failed to find object: No such file or directo

       

              jerzhang@redhat.com Yu Qi Zhang
              rhn-support-ssonigra Sonigra Saurab
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: