Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create two build configurations with the same name from two different namespaces (For example use: https://github.com/openshift/origin/tree/master/examples/sample-app) 2. Initiate a builds from both of them 3. Actual results: One of the builds will be connected to both build pods Expected results: Each one of the two builds should be connected to one build pod for its own namespace. Additional info:
Fix PR in: https://github.com/ManageIQ/manageiq-providers-openshift/pull/33
Verified on 5.9.0.10.20171121225911_a2209d2. On OpenShift: download the application-template-stibuild.json from https://github.com/openshift/origin/tree/master/examples/sample-app to /tmp oc new-project test --display-name="OpenShift 3 Sample" --description="This is an example project to demonstrate OpenShift v3" oc new-app /tmp/application-template-stibuild.json perform the above on second build with namespace test1. Each one of the two builds should be connected to one build pod for its own namespace. See attach.
Created attachment 1359153 [details] container builds