Bug 1515917 - IPA authentication causes issues on sat-clone
Summary: IPA authentication causes issues on sat-clone
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Clone
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-21 15:37 UTC by John Mitsch
Modified: 2019-09-26 16:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-19 17:23:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0330 0 normal SHIPPED_LIVE Satellite Maintenance bug fix update 2018-02-19 22:22:51 UTC

Description John Mitsch 2017-11-21 15:37:37 UTC 
2. If the IPA authentication (OS level) was configured on the old server and it is not configured on the new server then installer fails with error : 

The system does not seem to be IPA-enrolled at /usr/share/foreman-installer/modules/foreman/manifests/config.pp:63
Version-Release number of selected component (if applicable):
Comment 1 John Mitsch 2017-11-21 15:39:23 UTC 
Upstream issue is here: https://github.com/RedHatSatellite/satellite-clone/issues/268
Comment 2 Brad Buckingham 2017-11-30 15:48:51 UTC 
Since the upstream issue has been merged, moving this to POST.
Comment 4 John Mitsch 2017-12-18 14:48:04 UTC 
This didn't make it into 1.2.0, but will be in 1.2.1+
Comment 6 Peter Ondrejka 2018-02-08 13:37:01 UTC 
Verified on Maintenance snap 8, cloning from ipa-enabled backup does not cause problems as the "--foreman-ipa-authentication false" option is applied in the installer phase
Comment 9 errata-xmlrpc 2018-02-19 17:23:12 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-2018:0330
Note You need to log in before you can comment on or make changes to this bug.