Description of problem: This is a bit similar to https://bugzilla.redhat.com/show_bug.cgi?id=1469482 But one build will link to all the pods and the other will link to none. Some of the pods that are linked will be from a wrong namespace. Version-Release number of selected component (if applicable): How reproducible: similar to https://bugzilla.redhat.com/show_bug.cgi?id=1469482 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Pods should be linked from all builds that where initiated and from the same namespace. Additional info: Fixed by: https://github.com/ManageIQ/manageiq/pull/15575
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.
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 1359154 [details] containers builds