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

Incorrect field description for GCP Project Number on GCP WIF cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.17.z
    • Management Console
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When installing Loki Operator on GCP WIF clusters supporting CCO, it is seen that the field where GCP project number needs to be provided is described as 'GCP Pool ID'. This results is 2 fields having description of 'GCP Pool ID' which can cause confusion on installation.

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

      OCP 4.17 but it needs to be backported to versions supporting GCP WIF with CCO.

      How reproducible:

      Always

      Steps to Reproduce:

      1. Install Loki Operator on GCP WIF/STS cluster.

      Actual results:

      GCP Project Number needs to be provided under the input 'GCP Pool ID'

      Expected results:

      GCP Project number should have a matching field like 'GCP Project Number'

      Additional info:

      UI Screenshot attached.

        1. Screenshot 2024-12-06 at 1.35.35 PM.png
          Screenshot 2024-12-06 at 1.35.35 PM.png
          354 kB

            [OCPBUGS-45834] Incorrect field description for GCP Project Number on GCP WIF cluster

            Jianping Shu added a comment -

            rhn-support-kbharti This was implemented according to this interface doc. I suggest to get agreement in the document firstly. If it should be fixed, I think the right component is the console.

            Jianping Shu added a comment - rhn-support-kbharti This was implemented according to this interface doc . I suggest to get agreement in the document firstly. If it should be fixed, I think the right component is the console.

            Jeremiah Stuever added a comment -

            This looks to be specific to the Loki operator, which I am assuming is managed by logging.

            Jeremiah Stuever added a comment - This looks to be specific to the Loki operator, which I am assuming is managed by logging.

              amobrem Ali Mobrem
              rhn-support-kbharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: