Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-7851

Default TekonConfig is created when it should not

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Use the subscription in the description. Unfortunately, it is not always reproducible. May be there's a race condition?

      Show
      Use the subscription in the description. Unfortunately, it is not always reproducible. May be there's a race condition?

      OCP: 4.18
      OSP: 1.18.0

      Subscription is installed with:

      apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: openshift-pipelines-operator-rh
  namespace: openshift-operators
spec:
  channel: pipelines-1.18
  config:
    env:
    - name: AUTOINSTALL_COMPONENTS
      value: "false"
  installPlanApproval: Automatic
  name: openshift-pipelines-operator-rh
  source: redhat-operators
  sourceNamespace: openshift-marketplace

      The expectation is that the default tektonconfig is never created. The reality is that is it sometimes created.

              Unassigned Unassigned
              rarnaud@redhat.com Romain Arnaud
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: