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

The hypershift cli (hcp) reports an inaccurate OCP supported version


    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.14
    • HyperShift
    • Moderate
    • No
    • Hypershift Sprint 254
    • 1
    • False
    • Hide



      Description of problem:

          The self-managed hypershift cli (hcp) reports an inaccurate OCP supported version.
      For example, if I have a hypershift-operator deployed which supports OCP v4.14 and I build the hcp cli from the latest source code, when I execute "hcp -v", the cli tool reports the following. 
      $ hcp -v
      hcp version openshift/hypershift: 02bf7af8789f73c7b5fc8cc0424951ca63441649. Latest supported OCP: 4.16.0
      This makes it appear that the hcp cli is capable of deploying OCP v4.16.0, when the backend is actually limited to v4.14.0.
      The cli needs to indicate what the server is capable of deploying. Otherwise it appears that v4.16.0 would be deployable in this scenario, but the backend would not allow that. 

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


      How reproducible:


      Steps to Reproduce:

          1. download an HCP client that does not match the hypershift-operator backend
          2. execute 'hcp -v'
          3. the reported "Latest supported OCP" is not representative of the version the hypershift-operator actually supports     

      Actual results:


      Expected results:

           hcp cli reports a latest OCP version that is representative of what the deployed hypershift operator is capable of deploying. 

      Additional info:


            skuznets@redhat.com Steve Kuznetsov
            rhn-engineering-dvossel David Vossel
            Liangquan Li Liangquan Li
            0 Vote for this issue
            5 Start watching this issue