Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Simplified replica installation
Installing a replica no longer requires you to log in to the initial server, use the Directory Manager (DM) credentials, and copy the replica information file from the initial server to the replica. For example, this allows for easier provisioning using an external infrastructure management system, while retaining a reasonable level of security.
In addition, the "ipa-replica-install" utility can now also promote an existing client to a replica.
For details, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Linux_Domain_Identity_Authentication_and_Policy_Guide/index.html#install-replica
Note that the new functionality requires raising the domain level to `1`. See https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Linux_Domain_Identity_Authentication_and_Policy_Guide/index.html#domain-level
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2888
Current replica creation model calls for creation of a package on the existing replica and then delivering it to the new replica host being installed. A more robust approach that would allow easier migration between different versions is to have the following model.
Install a client on a future replica machine.
Join in to the domain
Install server bits using yum install
Run a command to promote the client to replica. As result of this command the client would connect to the existing master and pull in the data it needs rather than having a replica package being manually pre-created and delivered.
The benefit is that the replica being installed would be able to get the data it needs in the format in needs. It would reduce the need to deal with the cases when the master is versions 2.x and the replica is version 3.1.x.
Until this is implemented it makes sense to defer the support of the mixed domains between the versions.
Might be a problem for Fedora though...
Fixed upstream
master:
9e007edbd902a5395797ca0ca9a698033540d755 Remove unused kra option
6a0087aea176d1e1154b359fa262066896d663e3 Add low level helper to get domain level
42e859daa78396321d25e95107eabf35d46cdd91 Make checks for existing credentials reusable
2606f5aecd6ac0db31abb515b691529bb7eaf14e Allow to setup the CA when promoting a replica
102651b10afa144384db53b45fb558747a092d6d prevent operation on tombstones
fcb9854dcb047018a1904c7e6db655af0596e3ae handle multiple managed suffixes
80e11d24696c30ee311bd019ed39df8fc0f908a2 topology plugin configuration workaround
834b5fd513d799bb9fe2cbc29417ff8ec7357033 enable topology plugin on upgrade
fff31ca220311421f1ac8cef0888aaa892e97584 topology: manage ca replication agreements
86240938b58cd9bf85a96d34c39b55f6d59a36b8 Add function to extract CA certs for install
5761f73e2598dc404a3b51c6810e3dd250d2ba11 Allow ipa-replica-conncheck to use default creds
f7d1e4f9a21b0f3e63bd3bcd4a17acf749e0b208 Change DNS installer code to use passed in api
d03619fff3a1eb7d21c2ba21f8867ae8018779b8 Implement replica promotion functionality
2cd0d20a2a454369488b77e841a9cce643b26d34 Require a DS version that has working DNA plugin
463dda30679da9ac5eea5683984002989965e2a5 Add ipa-custodia service
98bf90e4cecb38fc72a0b598a6e6a50fee284f31 fix dsinstance.py:get_domain_level function
958996b9cc55b6e9ecdc23981e79599ec6826b4c Allow ipa-ca-install to use the new promotion code
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://rhn.redhat.com/errata/RHBA-2016-2404.html