Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1319791

Summary: Cannot access docker compute resource via compute profile.
Product: Red Hat Satellite Reporter: Oleksandr Shtaier <oshtaier>
Component: Container ManagementAssignee: Daniel Lobato Garcia <dlobatog>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, ehelms, jcallaha, mmccune
Target Milestone: UnspecifiedKeywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: http://projects.theforeman.org/issues/14391
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:28:06 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:
Attachments:
Description Flags
Screenshot with correct behavior for 6.1.z version
none
Screenshot with error for 6.2 none

Description Oleksandr Shtaier 2016-03-21 14:24:37 UTC
Description of problem:
Trying to open docker compute resource through compute profile interface. Get an exception in result

Version-Release number of selected component (if applicable):
6.2 SNAP4

How reproducible:
Always

Steps to Reproduce:
- Go to Infrastructure->Compute Resources
- Push 'New Compute Resource' button
- Input name
- Choose 'Docker' as a provider
- Specify 'http://localhost:2375' (for example) value in URL field
- Push 'Submit' button
- Go to Infrastructure->Compute Profiles
- Choose '1-Small' profile
- Select compute resource entity that was just created

Actual results:
Exception error is raised

Expected results:
Corresponding entity configuration is shown

Additional info:

Comment 1 Oleksandr Shtaier 2016-03-21 14:27:35 UTC
Created attachment 1138614 [details]
Screenshot with correct behavior for 6.1.z version

Comment 2 Oleksandr Shtaier 2016-03-21 14:28:04 UTC
Created attachment 1138615 [details]
Screenshot with error for 6.2

Comment 3 Oleksandr Shtaier 2016-03-21 14:30:16 UTC
There are no connection to https://bugzilla.redhat.com/show_bug.cgi?id=1223405. Just in case

Comment 5 Daniel Lobato Garcia 2016-03-30 07:12:00 UTC
Under review at https://github.com/theforeman/foreman-docker/pull/149

Comment 6 Bryan Kearney 2016-03-30 14:06:53 UTC
Upstream bug component is Container Management

Comment 7 Bryan Kearney 2016-04-01 18:09:22 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14391 has been closed
-------------
Daniel Lobato Garcia
Applied in changeset commit:foreman-docker|1aa3ddb3039a135fc7d303e69c5a389f84dc9ed3.

Comment 8 jcallaha 2016-04-06 19:41:26 UTC
Verified in Satellite 6.2 Beta Snap 6 Compose 2.

You can no longer choose Docker compute resources from the VM Attributes.

Comment 10 errata-xmlrpc 2016-07-27 09:28:06 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/RHBA-2016:1501