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

Empty error message when an invalid custom osImage is configured in Techpreview

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • Low
    • Yes
    • None
    • None
    • MCO Sprint 279
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          When an invalid custom osImage is configured in MCO, the reported error is empty  "%!w(<nil>)"

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

      4.21.0-0.nightly-2025-10-30-125804    

      How reproducible:

          Always

      Steps to Reproduce:

          1. Enable Techpreview
      
      $ oc patch featuregate cluster --type=merge -p '{"spec":{"featureSet": "TechPreviewNoUpgrade"}}'
      
          2. Create a MC to deploy an invalid custom osImage
      
      $ cat << EOF | oc create -f -
       kind: MachineConfig
       apiVersion: machineconfiguration.openshift.io/v1
       metadata:
         labels:
           machineconfiguration.openshift.io/role: "worker"
         name: "not-bootable-image-tc54052"
       spec:
         osImageURL: "quay.io/openshifttest/hello-openshift:1.2.0"
      EOF
          
      
          4. Wait for the mcp to become degraded

      Actual results:

          The reported error is empty: %!w(<nil>)"
      
      $ oc get mcp worker -oyaml
      ...
      
        - lastTransitionTime: "2025-10-31T10:55:01Z"
          message: 'Node ip-10-0-20-14.us-east-2.compute.internal is reporting: "Node ip-10-0-20-14.us-east-2.compute.internal
            upgrade failure. Failed to update OS to quay.io/openshifttest/hello-openshift:1.2.0
            after retries: %!w(<nil>)", Node ip-10-0-20-14.us-east-2.compute.internal is
            reporting: "Failed to update OS to quay.io/openshifttest/hello-openshift:1.2.0
            after retries: %!w(<nil>)"'     reason: ""
          status: "True"
          type: Degraded
      
      
      
      

      Expected results:

          The degraded message should show the right error causing the problem

      Additional info:

      It looks like it is related to https://issues.redhat.com/browse/OCPBUGS-52302    

              rh-ee-ijanssen Isabella Janssen
              sregidor@redhat.com Sergio Regidor de la Rosa
              None
              None
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: