+++ This bug was initially created as a clone of Bug #1796185 +++ Description of problem: When selecting to add a pipeline from a runtime in the Add flows, it negates the understanding of the resource type that the pipeline may be in reference to. Version-Release number of selected component (if applicable): Noticed in 4.4, will need to be put back into 4.3. How reproducible: Steps to Reproduce: 1. Once a Pipeline is added to the `openshift` namespace with the appropriate label tying it to a runtime (ie pipeline.openshift.io/runtime:java - for the java runtime) 2. Navigate to the +Add flow and import from Git (or Dockerfile) 3. Notice that selecting the java runtime gets you the associated pipeline from the `openshift` namespace 4. Change your Resource type (Deployment, Deployment Config, Knative - if installed) and the pipeline is unaffected Actual results: Unable to associate a pipeline that may include internals for deployment vs knative for instance. Expected results: Being able to associate a pipeline to both a runtime as well as a resource type. Additional info: Logged first here https://issues.redhat.com/browse/ODC-2880 but needs backport to 4.3
Bulk assigning all to Gajanan for verification.
Created attachment 1667211 [details] Enable pipelines for Knative and Kubernetes apps on import
Verified on build : 4.4.0-0.ci-2020-03-03-033811 Chrome browser: 76.0.3809.132
Created attachment 1667505 [details] Enable pipelines for Knative and Kubernetes apps on import-screenshot
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581