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

UPI docs do not reference correct internal api name

XMLWordPrintable

    • No
    • Sprint 255, Installer Sprint 256, Installer Sprint 257
    • 3
    • False
    • Hide

      None

      Show
      None
    • The UPI docs referenced names that no longer existed. The backend service for api-internal no longer contains the text backend-service in the name. No the resource names will match those in terraform.
    • Release Note Not Required
    • Proposed

      Description of problem:

      The MAPI GCP Code hasn't changed since 4.14, so if it were a MAPI issue I'd expect to see other things breaking.T
      
      he Installer doesn't seem to have changed either, however there's a discrepancy between what's created by 
      
      terraform: https://github.com/openshift/installer/blame/916b3a305691dcbf1e47f01137e0ceee89ed0f59/data/data/gcp/post-bootstrap/main.tf#L14 
      
      https://github.com/openshift/installer/blob/916b3a305691dcbf1e47f01137e0ceee89ed0f59/data/data/gcp/cluster/network/lb-private.tf#L10 
      
      and the UPI instructions 
      
      https://github.com/openshift/installer/blame/916b3a305691dcbf1e47f01137e0ceee89ed0f59/docs/user/gcp/install_upi.md#L560 
      
      https://github.com/openshift/installer/blob/916b3a305691dcbf1e47f01137e0ceee89ed0f59/upi/gcp/02_lb_int.py#L19

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

       

      How reproducible:

       

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

            rh-ee-bbarbach Brent Barbachem
            rh-ee-bbarbach Brent Barbachem
            Jianli Wei Jianli Wei
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: