Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-6211

Import from git as Serverless Service creates an incomplete BuildConfig (Secret is missing)

    XMLWordPrintable

Details

    • ODC Sprint 206
    • Medium

    Description

      Description of problem:

      When the user imports from Git and selects "Serverless Deployment" as resource type, the generated BuildConfig is incomplete and shows a warning alert when on the BuildConfig detail page.

      The warning blames a missing Secret "${service-name}-github-webhook-secret"

      Everything else (build and service start) works fine.

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

      1. OpenShift Serverless operator

      Steps to Reproduce

      1. Open developer perspective, Add page, Import from Git
      2. Enter a git URL
      3. As resources select "Serverless Deployment"
      4. Create
      5. Open navigation entry "Builds" and the new created "BuildConfig" (app name)

      Actual results:

      The BuildConfig detail page shows a warning between the general infos and webhooks.

      There is 1 warning alert.
      Error: secrets "nodeinfo-serverless-github-webhook-secret" not found
      

      The BuildConfig links two webhooks. The generic webhook is clickable, the GitHub webhook is not clickable.

      The YAML tab lists two secrets for triggers. Only one of the both secrets is created.

        triggers:
          - type: Generic
            generic:
              secretReference:
                name: nodeinfo-serverless-generic-webhook-secret       # exists
          - type: GitHub
            github:
              secretReference:
                name: nodeinfo-serverless-github-webhook-secret        # does not exist
          - type: ImageChange
            imageChange:
              lastTriggeredImageID: >-
                image-registry.openshift-image-registry.svc:5000/....
      

      Expected results:

      The BuildConfig should now show a warning that a secret is missing.

      Both secrets should be created OR the second trigger should not be created.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      4.9 master (tested with console commit c0ba821c0b385db10107f4413d67abe01f89f0c3)

      Additional info:

      None

      Attachments

        Activity

          People

            mdsaud Mohammed Saud (Inactive)
            cjerolim Christoph Jerolimov
            Gajanan More Gajanan More (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: