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

[4.13] Incorrect link to KCS for Automatic CSI driver warning

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 4.13.z, 4.12.z
    • Storage / Operators
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

       cluster running on version 4.13 is showing incorrect link to the kcs 
      
          - lastTransitionTime: "2024-07-04T14:01:16Z"
            message: vSphere CSI migration will be enabled in Openshift-4.14. Your cluster
              appears to be using in-tree vSphere volumes and is on a vSphere version that
              has CSI migration related bugs. See - https://access.redhat.com/node/7011683
              for more information, before upgrading to 4.14.
            reason: AdminAckRequired
            status: "False"
            type: Upgradeable
      
      The correct link to the doc should be this
      
      https://docs.redhat.com/en/documentation/openshift_container_platform/4.14/html/storage/using-container-storage-interface-csi#new-installations-of-openshift-container-platform
      
      

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

          4.12 and 4.13

      How reproducible:

          

      Steps to Reproduce:

          1 install a cluster with 4.13 or 4.13 
          2. have an intree pvc 
          3. you will see a warning in the clusterversion yaml
          

      Actual results:

          The oc get clusterversion -o yaml shows warning with incorrect url to refer

      Expected results:

      The url should be correct    

      Additional info:

          

              rhn-support-tsmetana Tomas Smetana
              rhn-support-ssonigra Sonigra Saurab
              Wei Duan Wei Duan
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: