Bug 1698182

Summary: [RFE] Remove foreman docker
Product: Red Hat Satellite Reporter: Bryan Kearney <bkearney>
Component: Container Management - RuntimeAssignee: Daniel Lobato Garcia <dlobatog>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: egolov, lhellebr, mhulan, rplevka, spetrosi, trichard
Target Milestone: 6.6.0Keywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_docker-5.0.0, rubygem-foreman_maintain-0.4.3 Doc Type: Deprecated Functionality
Doc Text:
In Red Hat Satellite 6.6, the foreman_docker plug-in has been removed, therefore it is no longer possible to provision containers.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 12:47:18 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: 1716613    

Comment 4 Lukáš Hellebrandt 2019-06-03 09:45:21 UTC
Why is this still NEW and not set to 6.6?

Comment 12 Lukáš Hellebrandt 2019-07-30 14:38:02 UTC
Verified with Sat 6.6 snap 13.

Couldn't find any bogus API endpoints, hammer correctly states the related commands are not supported (they are still present in hammer for technical reasons, consulted with devels and it's expected), WebUI doesn't have Containers menu item and it's not possible to add a CR of type Docker.

Note that I haven't tested upgrades.

There is some suboptimal behavior in Hammer which I don't consider a blocker and will report in another BZ.

Comment 14 errata-xmlrpc 2019-10-22 12:47:18 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-2019:3172