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

[gcp] when the optional Service Usage API is disabled, IPI installation cannot succeed

    XMLWordPrintable

Details

    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      By default, {product-title} {product-version} enables the Service Usage API, which has a console service name of `serviceusage.googleapis.com`, during cluster installation operations. Before {product-title} {product-version}, the Service Usage API was an optional component that when disabled could lead to `openshift-install` failures. These failures were caused by an insufficient number of running compute machines.

      (link:https://issues.redhat.com/browse/OCPBUGS-3307[*OCPBUGS-3307*])
      Show
      By default, {product-title} {product-version} enables the Service Usage API, which has a console service name of `serviceusage.googleapis.com`, during cluster installation operations. Before {product-title} {product-version}, the Service Usage API was an optional component that when disabled could lead to `openshift-install` failures. These failures were caused by an insufficient number of running compute machines. (link: https://issues.redhat.com/browse/OCPBUGS-3307 [* OCPBUGS-3307 *])
    • Bug Fix
    • Done

    Description

      This is a clone of issue OCPBUGS-1704. The following is the description of the original issue:
      —
      Description of problem:

      According to OCP 4.11 doc (https://docs.openshift.com/container-platform/4.11/installing/installing_gcp/installing-gcp-account.html#installation-gcp-enabling-api-services_installing-gcp-account), the Service Usage API (serviceusage.googleapis.com) is an optional API service to be enabled. But, the installation cannot succeed if this API is disabled.

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

      4.12.0-0.nightly-2022-09-25-071630

      How reproducible:

      Always, if the Service Usage API is disabled in the GCP project.

      Steps to Reproduce:

      1. Make sure the Service Usage API (serviceusage.googleapis.com) is disabled in the GCP project.
2. Try IPI installation in the GCP project.

      Actual results:

      The installation would fail finally, without any worker machines launched.

      Expected results:

      Installation should succeed, or the OCP doc should be updated.

      Additional info:

      Please see the attached must-gather logs (http://virt-openshift-05.lab.eng.nay.redhat.com/jiwei/jiwei-0926-03-cnxn5/) and the sanity check results. 
FYI if enabling the API, and without changing anything else, the installation could succeed. 

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-4325 [gcp] when the optional Service Usage API is disabled, IPI installation cannot succeed

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          clones

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1704 [gcp] when the optional Service Usage API is disabled, IPI installation cannot succeed

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-1704 [gcp] when the optional Service Usage API is disabled, IPI installation cannot succeed

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          links to

          GitHub openshift/installer#6565: [release-4.12] OCPBUGS-3307: gcp: fail during validation if service usage is not enabled

          Activity

            People

              rdossant Rafael Fonseca dos Santos
              openshift-crt-jira-prow OpenShift Prow Bot
              Jianli Wei Jianli Wei
              Darragh Fitzmaurice Darragh Fitzmaurice
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: