Bug 1181694

Summary: [RFE] foreman-prepare-realm should support FreeIPA 4
Product: Red Hat Satellite Reporter: Stephen Benjamin <stbenjam>
Component: Foreman ProxyAssignee: Stephen Benjamin <stbenjam>
Status: CLOSED ERRATA QA Contact: Kedar Bidarkar <kbidarka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: asimonel, bbuckingham, bkearney, caugello, kbidarka, sthirugn
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/8278
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:21:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stephen Benjamin 2015-01-13 15:37:40 UTC
FreeIPA 4 has some major changes to the permission system, foreman-prepare-realm will need to handle creating the Smart Proxy role a bit differently.

Comment 1 Stephen Benjamin 2015-01-13 15:37:42 UTC
Created from redmine issue http://projects.theforeman.org/issues/8278

Comment 2 Stephen Benjamin 2015-01-13 15:39:45 UTC
RHEL 7.1 is now shipping with IdM based on FreeIPA 4.1.  It would be useful I think if this could be QE'd for Satellite 6.1, if possible.

foreman-prepare-realm was updated to handle this new permission system upstream.

Comment 4 Kedar Bidarkar 2015-03-18 11:11:05 UTC
The  script foreman-prepare_realm got executed properly without any errors while working with sat6.1 on RHEL7.1 communicating with RHEL7.1


VERIFIED with sat6.1 beta snap6 compose2

Comment 7 Stephen Benjamin 2015-03-29 19:51:14 UTC
*** Bug 1206457 has been marked as a duplicate of this bug. ***

Comment 9 Bryan Kearney 2015-08-11 13:29:42 UTC
This bug is slated to be released with Satellite 6.1.

Comment 10 errata-xmlrpc 2015-08-12 05:21:51 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