Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-3005

ApplicationSet controller receives x509: certificate signed by unknown authority, when using scmProvider with GitLab

XMLWordPrintable

    • False
    • None
    • False

      Description of problem:

      ApplicationSet controller receives x509: certificate signed by unknown authority when using scmProvider with GitLab

       

      error when creating new applicationSet: error listing repos: error listing projects for 126: Get "https://<url>/api/v4/groups/": x509: certificate signed by unknown authority yaml info: generators: - scmProvider: gitlab: group: "126"
      

      We have done the following:

      1. add a self-sign certificate in argocd
      2. add insecure in yaml & secrets

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

       # Create an ApplicationSet Controller for scm to provide a generator, for example yaml attached

      For ref: Similar issue raised https://github.com/argoproj/argo-cd/issues/9607

      Actual results:

      Throws above mentioned error

      Expected results:

      Expected the application set controller to be able to communicate with GitLab server API's to list repositories and automate ArgoCD application generation.

      Reproducibility (Always/Intermittent/Only Once): Always

      Acceptance criteria: 

      • Fix the upstream issue https://github.com/argoproj/argo-cd/issues/9607
      • Get the fix into an Argo CD release
      • Consume the version of Argo CD that has the fix
      • In case of fix taking more time, support the workaround in the gitops-operator that currently works for the upstream project.

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

      applicationSet.yaml

       *

            Unassigned Unassigned
            rhn-support-sburhade Satyam Burhade
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: