Bug 1474076

Summary: Builds are connected to pods from different namespaces when builds have the same names
Product: Red Hat CloudForms Management Engine Reporter: Erez Freiberger <efreiber>
Component: ProvidersAssignee: Erez Freiberger <efreiber>
Status: CLOSED CURRENTRELEASE QA Contact: brahmani
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8.0CC: efreiber, gblomqui, jfrey, jhardy, obarenbo, simaishi
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1478568 (view as bug list) Environment:
Last Closed: 2018-03-06 14:43:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Container Management Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1478568    
Attachments:
Description Flags
containers builds none

Description Erez Freiberger 2017-07-23 15:54:02 UTC 
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
Comment 4 Dave Johnson 2017-07-26 00:27:59 UTC 
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.
Comment 6 brahmani 2017-11-26 13:42:44 UTC 
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.
Comment 7 brahmani 2017-11-26 13:43:14 UTC 
Created attachment 1359154 [details]
containers builds