Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1192614 - Wrong Docker Compute resource getting provisioned
Summary: Wrong Docker Compute resource getting provisioned
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: David Davis
QA Contact: Elyézer Rezende
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1190289
TreeView+ depends on / blocked
 
Reported: 2015-02-13 20:39 UTC by Partha Aji
Modified: 2019-04-01 20:26 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1190059
Environment:
Last Closed: 2015-08-12 05:25:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9382 0 None None None 2016-04-22 15:56:23 UTC
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

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
Note You need to log in before you can comment on or make changes to this bug.