Bug 1633661 - realm provisioning is broken in default provisioning template
Summary: realm provisioning is broken in default provisioning template
Keywords:
Status: CLOSED DUPLICATE of bug 1635680
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-27 13:33 UTC by Fred van Zwieten
Modified: 2018-10-04 12:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-04 12:08:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Fred van Zwieten 2018-09-27 13:33:54 UTC
Description of problem:
The line in the "Kickstart Default" provisioning template that selects for including the freeipa snippet is wrong and the snippet will never be activated. This is because 6.4 now support AD realms and as a result has renamed freeipa into "Red Hat Identity Management". However, this has not been also changed in this template

Version-Release number of selected component (if applicable):
6.4.0 snap 24

How reproducible:
Deploy host on a 6.4.0 satellite with freeipa realm support configured

Steps to Reproduce:
1.
2.
3.

Actual results:
Host created in freeipa, but not enrolled and no DNS records.

Expected results:
Host created in freeipa, enrolled and DNS records created.


Additional info:
The actual line is:
<% if host_enc['parameters']['realm'] && @host.realm && @host.realm.realm_type == 'FreeIPA' -%>

This must be:
<% if host_enc['parameters']['realm'] && @host.realm && @host.realm.realm_type == 'Red Hat Identity Management' -%>

NOTE: maybe other templates have this issue as well

Comment 4 Stephen Benjamin 2018-10-04 12:08:14 UTC
Tracked by another BZ, actually.

*** This bug has been marked as a duplicate of bug 1635680 ***


Note You need to log in before you can comment on or make changes to this bug.