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

x86 node gets tainted unexpectedly after OpenShift upgrade from 4.16.38 to 4.17.25 in multi-architecture (x86 + s390x) cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 4.17.z
    • Multi-Arch
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          

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

          

      How reproducible:

          

      Steps to Reproduce:

          1.Create a openshift sandbox cluster(4.16.x) having few node on s390x and others on x86.
          2.upgrade it to next recommended version.
          3.You will find the issue
          

      Actual results:

      We encountered an issue while upgrading our OpenShift cluster from version 4.16.38 to 4.17.25. The cluster consists of 4 nodes, with 1 node on x86 architecture and 3 nodes on s390x.

      After the upgrade, the x86 node was automatically tainted, which was not expected. This taint caused certain workloads to be unschedulable on the x86 node. No manual tainting or node role changes were done during the upgrade process.

       

      Expected results:

          Should behave normally.

      Additional info:

          

              kdo@redhat.com Kha Do (Inactive)
              drkumar0221 Rajesh Kumar
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: