Bug 2229134

Summary:	RFE: check for krbLastSuccessfulAuth being enabled
Product:	Red Hat Enterprise Linux 9	Reporter:	François Cami <fcami>
Component:	ipa-healthcheck	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED MIGRATED	QA Contact:	ipa-qe
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.2	CC:	fcami
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 22:59:19 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description François Cami 2023-08-04 10:00:59 UTC

Description of problem:

We're still seeing cases where krbLastSuccessfulAuth is causing performance issues.

I'll quote the upstream issue:
https://pagure.io/freeipa/issue/5313
"Even if this attribute is skipped in fractional replication, all the changes
are sent to changelog and replication has to browse them to decide whether to
skip or not."

Would it be possible to check for this?


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

Current git main, considering:
$ grep -nr krbLastSuccessfulAuth .
$ git log | head -n1
commit 11c77a199304fba4f430e9386593477f37652f23

Comment 2 Rob Crittenden 2023-08-04 13:07:34 UTC

In other words you're asking for a check to display a WARNING if "KDC:Disable Last Success" is not in the ipaConfigString attribute?

Comment 3 François Cami 2023-08-04 13:33:29 UTC

Hi Rob, yes, exactly that, please.

Comment 4 RHEL Program Management 2023-09-18 22:54:13 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-18 22:59:19 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.