Bug 1192614

Summary: Wrong Docker Compute resource getting provisioned
Product: Red Hat Satellite Reporter: Partha Aji <paji>
Component: ProvisioningAssignee: David Davis <daviddavis>
Status: CLOSED ERRATA QA Contact: Elyézer Rezende <erezende>
Severity: high Docs Contact:
Priority: high    
Version: UnspecifiedCC: bbuckingham, cwelton, daviddavis, dlobatog, erezende, jmontleo, katello-qa-list, mmccune, paji, sghai, sthirugn
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/9382
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1190059 Environment:
Last Closed: 2015-08-12 05:25:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1190289    

Comment 1 Partha Aji 2015-02-13 20:41:49 UTC
Created redmine issue http://projects.theforeman.org/issues/9382 from this bug

Comment 2 RHEL Program Management 2015-02-13 20:43:22 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 4 Bryan Kearney 2015-02-13 21:05:22 UTC
Upstream bug assigned to daviddavis

Comment 5 Bryan Kearney 2015-03-18 19:32:32 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/9382 has been closed
-------------
David Davis
Applied in changeset commit:foreman-docker|5397ee73e891b8c9b9a2cda87a26954982f59133.

Comment 8 Elyézer Rezende 2015-03-24 15:38:02 UTC
Verified on: Satellite-6.1.0-RHEL-6-20150320.1

Steps to verify:
1. Created a Product, added a docker repo to it, synced the repo
2. Created a computer resource pointing to a valid docker service
3. Create a compute resource pointing to a not valid docker service
4. Went to Container > New Container, selected the not valid docker compute resource and searched for busybox on the Docker Hub tab
5. Went to Container > New Container again, but this time selected the docker repo from the previously created product and finished the wizard.
6. Powered on the created container from step 5
7. Checked docker ps on the valid docker compute resource

Comment 9 Bryan Kearney 2015-08-11 13:19:49 UTC
This bug is slated to be released with Satellite 6.1.

Comment 10 errata-xmlrpc 2015-08-12 05:25:49 UTC
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/RHSA-2015:1592