Bug 1192614 – Wrong Docker Compute resource getting provisioned

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1192614 - Wrong Docker Compute resource getting provisioned

Summary:	Wrong Docker Compute resource getting provisioned

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Provisioning (Show other bugs)
Sub Component:
Version:	Unspecified
Hardware:	Unspecified Unspecified

Priority	high Severity high (vote)
Target Milestone:	Beta
Target Release:	Unused
Assigned To:	David Davis
QA Contact:	Elyézer Rezende
Docs Contact:

URL:	http://projects.theforeman.org/issues...
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:	1190289
	Show dependency tree / graph

Reported:	2015-02-13 15:39 EST by Partha Aji
Modified:	2017-02-23 15:30 EST (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:	1190059
Environment:
Last Closed:	2015-08-12 01:25:49 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	9382	None	None	None	2016-04-22 11:56 EDT
Red Hat Product Errata	RHSA-2015:1592	normal	SHIPPED_LIVE	Important: Red Hat Satellite 6.1.1 on RHEL 6	2015-08-12 05:04:35 EDT

Groups: None (edit)

Comment 1 Partha Aji 2015-02-13 15:41:49 EST

Created redmine issue http://projects.theforeman.org/issues/9382 from this bug

Comment 2 RHEL Product and Program Management 2015-02-13 15:43:22 EST

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 16:05:22 EST

Upstream bug assigned to daviddavis@redhat.com

Comment 5 Bryan Kearney 2015-03-18 15:32:32 EDT

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 11:38:02 EDT

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 09:19:49 EDT

This bug is slated to be released with Satellite 6.1.

Comment 10 errata-xmlrpc 2015-08-12 01:25:49 EDT

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.