Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-38194

HCP CLI should not directly inspect the release image

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-1310 - [GA] HCP OpenShift Virtualization Disconnected
    • No
    • ---
    • ---
    • CNV I/U Operators Sprint 249, CNV I/U Operators Sprint 250, CNV I/U Operators Sprint 251, CNV I/U Operators Sprint 253

      Description of problem:

      HCP CLI is trying to directly inspect (client side) the release image,
      this cause some troubles when using it on disconnected environments because:
      1. the HCP CLI client should be able to directly reach the internal mirror registry and this could require additional configuration (a proxied access to the api server of the management server is not enough)
      2. the HCP CLI client should explicitly consume the pull secret of the internal mirror registry
      3. the HCP CLI client should explicitly consume the internal CA used to sign the TLS cert of the internal mirror registry
      

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

      4.14, 4.15, 4.16...
      

      How reproducible:

      100%
      

      Steps to Reproduce:

      1. run somthing like `hcp create cluster kubevirt --name simone2 --node-pool-replicas 2 --memory 16Gi --cores 4 --root-volume-size 64 --namespace local-cluster --release-image virthost.ostest.test.metalkube.org:5000/localimages/local-release-image@sha256:f50aca7690d197bcd2037bcb88c10237455ad61811158259496031426d9f833b` where the release-image is hosted on an internal mirror registry that cannot be directly reached from the client
      2.
      3.
      

      Actual results:

      Error: failed to default network: failed to get version for release image virthost.ostest.test.metalkube.org:5000/localimages/local-release-image@sha256:f50aca7690d197bcd2037bcb88c10237455ad61811158259496031426d9f833b: failed to get version information from virthost.ostest.test.metalkube.org:5000/localimages/local-release-image@sha256:f50aca7690d197bcd2037bcb88c10237455ad61811158259496031426d9f833b: failed to extract release metadata: failed to get repo setup: failed to create repository client for https://virthost.ostest.test.metalkube.org:5000: Get "https://virthost.ostest.test.metalkube.org:5000/v2/": dial tcp: lookup virthost.ostest.test.metalkube.org: no such host
      failed to default network: failed to get version for release image virthost.ostest.test.metalkube.org:5000/localimages/local-release-image@sha256:f50aca7690d197bcd2037bcb88c10237455ad61811158259496031426d9f833b: failed to get version information from virthost.ostest.test.metalkube.org:5000/localimages/local-release-image@sha256:f50aca7690d197bcd2037bcb88c10237455ad61811158259496031426d9f833b: failed to extract release metadata: failed to get repo setup: failed to create repository client for https://virthost.ostest.test.metalkube.org:5000: Get "https://virthost.ostest.test.metalkube.org:5000/v2/": dial tcp: lookup virthost.ostest.test.metalkube.org: no such host
      

      Expected results:

      No client side errors since the hcp client should not directly try to inspect the release image
      

      Additional info:

      Ongoing fix here: https://github.com/openshift/hypershift/pull/3548
      

            rhn-engineering-dvossel David Vossel
            stirabos Simone Tiraboschi
            Satheesaran Sundaramoorthi Satheesaran Sundaramoorthi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: