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.

Bug 2148249

Summary: ipa-client-install does not maintain server affinity during installation [rhel-7.9.z]
Product: Red Hat Enterprise Linux 7 Reporter: Trivino <ftrivino>
Component: ipaAssignee: Florence Blanc-Renaud <frenaud>
Status: CLOSED ERRATA QA Contact: Ganna Kaihorodova <gkaihoro>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: frenaud, gkaihoro, kpfleming, mjurasek, rakkumar, rcritten, tscherf, tsorense
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: gkaihoro: needinfo+
pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.6.8-5.el7_9.13 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-25 13:26:44 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 Trivino 2022-11-24 17:43:23 UTC
Cloned from upstream: https://pagure.io/freeipa/issue/9228

### Issue
ipa-client-install generates a temporary krb5.conf with a single KDC configured for ipa-join call. Once that is completed the temporary configuration is dropped and a full one is created, enabling DNS discovery by default.

A number of Kerberos operations occur after that, including connecting to the IPA API.

This can fail if a different server is picked via DNS and the ipa-client-install operations are faster than replication. This can lead to failures due to unknown hosts.

This was discovered by performance testing to determine how many simultaneous client installations can be performed. It was found that when additional IPA servers were added the capacity unexpectedly went down. It is this replication race that is the underlying problem.

The proposal is to retain the temporary configuration until nearer the end of installation and then write the final one.

#### Steps to Reproduce
1. Install IPA + 1 or more replicas
2. Run simultaneous client installations. It sometimes doesn't require many. It's race so unpredictable

#### Actual behavior
On the client side it will fail with a message that the TGT has been revoked.

gssapi.raw.misc.GSSError: Major (851968): Unspecified GSS failre.  Minor code may provide more informatino, Minor (2529638932): TGT has been revoked

The server side logs "PAC issue: ipadb_get_principal_failed "
(what do you expect to happen)

#### Expected behavior

Scale enrollments with additional servers.

#### Version/Release/Distribution

Tested on Fedora 36 with 4.9.10-3.fc36

Comment 3 Florence Blanc-Renaud 2022-11-25 08:55:44 UTC
*** Bug 2148250 has been marked as a duplicate of this bug. ***

Comment 4 Florence Blanc-Renaud 2022-11-25 08:56:54 UTC
*** Bug 2148253 has been marked as a duplicate of this bug. ***

Comment 5 Florence Blanc-Renaud 2022-11-25 08:57:09 UTC
*** Bug 2148256 has been marked as a duplicate of this bug. ***

Comment 6 Florence Blanc-Renaud 2022-11-25 08:59:19 UTC
*** Bug 2148367 has been marked as a duplicate of this bug. ***

Comment 7 Florence Blanc-Renaud 2022-11-25 09:00:03 UTC
*** Bug 2148368 has been marked as a duplicate of this bug. ***

Comment 8 Florence Blanc-Renaud 2022-11-25 09:06:31 UTC
Upstream ticket https://pagure.io/freeipa/issue/9228

Fixed upstream
master:
    https://pagure.io/freeipa/c/9d9d925b14dbf627546c51c47f6d4e7827645610 Defer creating the final krb5.conf on clients

ipa-4-10:
    https://pagure.io/freeipa/c/3cbf2b25422100cc4105dfb09ee8c7bf87232198 Defer creating the final krb5.conf on clients

ipa-4-9:
    https://pagure.io/freeipa/c/69413325158a3ea06d1491acd77ee6e0955ee89a Defer creating the final krb5.conf on clients

Comment 31 errata-xmlrpc 2023-04-25 13:26:44 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 (ipa bug fix and enhancement update), 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-2023:1990