Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-5920

Got "GitLab API error" when add gitlab build trigger in quay 3.8.11

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Normal
    • None
    • quay-v3.8.11
    • quay-builder
    • None
    • False
    • None
    • False
    • 0

    Description

      Description of problem:

      When add gitlab build trigger in quay 3.8.11, got a popup windows and it shows "GitLab API error". 
      But use the same gitlab application scopes setting to create gitlab build trigger in quay 3.9.0, everything works well.

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

      quay-operator-bundle-container-v3.8.11-20
      Index image v4.13: registry-proxy.engineering.redhat.com/rh-osbs/iib:551769
      registry.redhat.io/quay/quay-operator-rhel8@sha256:5d89410badfa0b6616ed7c8a94d42bcc6156b7fa20341cc004641288d6eb7319
      registry.redhat.io/quay/quay-rhel8@sha256:434581caa2ce03221ffd060c3f2972de315a41f9e28d40a877d45a5b81535e21
      

      How reproducible:

      always

      Steps to Reproduce:
      1. Configure a gitlab application to generate a client ID and client secret. Open all accesses in the application scopes 

      gitlab application settings

       

      2. create a build environment with quay 3.8.11

      .......
      FEATURE_BUILD_SUPPORT: True
      FEATURE_GITLAB_BUILD: true
      GITLAB_TRIGGER_CONFIG:
          CLIENT_ID: e622....
          CLIENT_SECRET: c...9 
      GITLAB_TRIGGER_KIND:
          GITLAB_ENDPOINT: https://gitlab.com/
      BUILDMAN_HOSTNAME: quayregistry-quay-builder-quay-enterprise.apps.whu413osp03.qe.devcluster.openshift.com:443
      BUILD_MANAGER:
      - ephemeral
      - ALLOWED_WORKER_COUNT: 3 
        ORCHESTRATOR_PREFIX: buildman/production/
        JOB_REGISTRATION_TIMEOUT: 600
        ORCHESTRATOR:
          REDIS_HOST: quayregistry-quay-redis
          REDIS_PASSWORD: "" 
          REDIS_SSL: false
          REDIS_SKIP_KEYSPACE_EVENT_SETUP: false
        EXECUTORS:
        - EXECUTOR: kubernetes
          DEBUG: true
          K8S_API_SERVER: api.whu412bm02.qe.devcluster.openshift.com:6443 
          K8S_API_TLS_CA: /conf/stack/extra_ca_certs/build_cluster.crt
          VOLUME_SIZE: 8G
          KUBERNETES_DISTRIBUTION: openshift
          CONTAINER_MEMORY_LIMITS: 5120Mi
          CONTAINER_CPU_LIMITS: 1000m
          CONTAINER_MEMORY_REQUEST: 3968Mi
          CONTAINER_CPU_REQUEST: 500m
          NODE_SELECTOR_LABEL_KEY: type 
          NODE_SELECTOR_LABEL_VALUE: builder 
          CONTAINER_RUNTIME: podman
          BUILDER_NAMESPACE: builder 
          SERVICE_ACCOUNT_NAME:  quay-builder  
          SERVICE_ACCOUNT_TOKEN: e..o
          QUAY_USERNAME: '...6'
          QUAY_PASSWORD: e...8 
          WORKER_IMAGE:  brew.registry.redhat.io/rh-osbs/quay-quay-builder-rhel8
          WORKER_TAG: v3.8.11 
          BUILDER_VM_CONTAINER_IMAGE: brew.registry.redhat.io/rh-osbs/quay-quay-builder-qemu-rhcos-rhel8:v3.8.11
          SETUP_TIME: 180
          MINIMUM_RETRY_THRESHOLD: 0
          SSH_AUTHORIZED_KEYS:
          - ssh-rsa A..e
      USERFILES_LOCATION: default
      USERFILES_PATH: userfiles
      .............

       

      3. Tried to add a gitlab build trigger  in "user1_build_test/gitlab"  repository

       Actual results:

      Got a popup windows with "GitLab API error. Please contact support" when create a gitlab build trigger.

      after clicking Continue button

      Expected results:

      The gitlab build trigger should be created successfully.

      Additional info:

      With the same gitlab application setting, create gitlab build trigger in quay 3.9.0, the trigger can be created successfully 

      gitlab application settings for quay 3.9.0

      create gitlab build trigger in quay 3.9.0

       

      Attach quay pod log in the  attachments. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            rhwhu Weihua Hu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: