Bug 1319791
Summary: | Cannot access docker compute resource via compute profile. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Oleksandr Shtaier <oshtaier> | ||||||
Component: | Container Management | Assignee: | Daniel Lobato Garcia <dlobatog> | ||||||
Status: | CLOSED ERRATA | QA Contact: | jcallaha | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 6.2.0 | CC: | bbuckingham, ehelms, jcallaha, mmccune | ||||||
Target Milestone: | Unspecified | Keywords: | 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
Oleksandr Shtaier
2016-03-21 14:24:37 UTC
Created attachment 1138614 [details]
Screenshot with correct behavior for 6.1.z version
Created attachment 1138615 [details]
Screenshot with error for 6.2
There are no connection to https://bugzilla.redhat.com/show_bug.cgi?id=1223405. Just in case Under review at https://github.com/theforeman/foreman-docker/pull/149 Upstream bug component is Container Management 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. Verified in Satellite 6.2 Beta Snap 6 Compose 2. You can no longer choose Docker compute resources from the VM Attributes. 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 |