Recently (not sure exactly when) I began seeing indexing errors on starting freeipa and when running ipa-healthcheck. I noticed that freeipa was upgraded in F43, so I upgraded from F42 to F43, but it didn't change the errors. There is a similar issue from October 2025, and I'm not sure if this is a regression or something new. From ipa-healthcheck:
[
  {
    "source": "ipahealthcheck.ds.backends",
    "check": "BackendsCheck",
    "result": "CRITICAL",
    "uuid": "aff0ac5d-5a61-4b98-9fa5-922327c4f7c8",
    "when": "20260204212241Z",
    "duration": "0.146653",
    "kw": {
      "key": "DSBLE0007",
      "items": [
        "cn=changelog"
      ],
      "msg": "System indexes are essential for proper directory server operation. Missing or\nincorrectly configured system indexes can lead to poor search performance, replication\nissues, and other operational problems.\n\nThe following system indexes should be present with correct configuration:\n- entryrdn: index type 'subtree'\n- parentid: index type 'eq' with matching rule 'integerOrderingMatch'\n- ancestorid: index type 'eq' with matching rule 'integerOrderingMatch'\n- objectClass: index type 'eq'\n- aci: index type 'pres'\n- nscpEntryDN: index type 'eq'\n- nsUniqueId: index type 'eq'\n- nsds5ReplConflict: index types 'eq', 'pres'\n- nsCertSubjectDN: index type 'eq'\n- numsubordinates: index type 'pres'\n- nsTombstoneCSN: index type 'eq'\n- targetuniqueid: index type 'eq'\n- changeNumber: index type 'eq' with matching rule 'integerOrderingMatch'\n- entryusn: index type 'eq' with matching rule 'integerOrderingMatch'\n\nCurrent discrepancies:\n- Index parentid missing matching rule: integerOrderingMatch\n- Index parentid missing fine grain definition of IDs limit: integerOrderingMatch\n"
    }
  },
  {
    "source": "ipahealthcheck.ds.backends",
    "check": "BackendsCheck",
    "result": "CRITICAL",
    "uuid": "458f139f-19bd-480d-b502-8d41955a6fe8",
    "when": "20260204212241Z",
    "duration": "0.146663",
    "kw": {
      "key": "DSBLE0007",
      "items": [
        "o=ipaca"
      ],
      "msg": "System indexes are essential for proper directory server operation. Missing or\nincorrectly configured system indexes can lead to poor search performance, replication\nissues, and other operational problems.\n\nThe following system indexes should be present with correct configuration:\n- entryrdn: index type 'subtree'\n- parentid: index type 'eq' with matching rule 'integerOrderingMatch'\n- ancestorid: index type 'eq' with matching rule 'integerOrderingMatch'\n- objectClass: index type 'eq'\n- aci: index type 'pres'\n- nscpEntryDN: index type 'eq'\n- nsUniqueId: index type 'eq'\n- nsds5ReplConflict: index types 'eq', 'pres'\n- nsCertSubjectDN: index type 'eq'\n- numsubordinates: index type 'pres'\n- nsTombstoneCSN: index type 'eq'\n- targetuniqueid: index type 'eq'\n- entryusn: index type 'eq' with matching rule 'integerOrderingMatch'\n\nCurrent discrepancies:\n- Index parentid missing matching rule: integerOrderingMatch\n- Index parentid missing fine grain definition of IDs limit: integerOrderingMatch\n"
    }
  },
  {
    "source": "ipahealthcheck.ds.backends",
    "check": "BackendsCheck",
    "result": "CRITICAL",
    "uuid": "705d8957-c9db-479b-938a-f00ed9dc2cad",
    "when": "20260204212241Z",
    "duration": "0.146666",
    "kw": {
      "key": "DSBLE0007",
      "items": [
        "dc=ferree-clark,dc=org"
      ],
      "msg": "System indexes are essential for proper directory server operation. Missing or\nincorrectly configured system indexes can lead to poor search performance, replication\nissues, and other operational problems.\n\nThe following system indexes should be present with correct configuration:\n- entryrdn: index type 'subtree'\n- parentid: index type 'eq' with matching rule 'integerOrderingMatch'\n- ancestorid: index type 'eq' with matching rule 'integerOrderingMatch'\n- objectClass: index type 'eq'\n- aci: index type 'pres'\n- nscpEntryDN: index type 'eq'\n- nsUniqueId: index type 'eq'\n- nsds5ReplConflict: index types 'eq', 'pres'\n- nsCertSubjectDN: index type 'eq'\n- numsubordinates: index type 'pres'\n- nsTombstoneCSN: index type 'eq'\n- targetuniqueid: index type 'eq'\n- entryusn: index type 'eq' with matching rule 'integerOrderingMatch'\n\nCurrent discrepancies:\n- Index parentid missing matching rule: integerOrderingMatch\n- Index parentid missing fine grain definition of IDs limit: integerOrderingMatch\n"
    }
  },
  {
    "source": "ipahealthcheck.ipa.dna",
    "check": "IPADNARangeCheck",
    "result": "WARNING",
    "uuid": "7a3f9391-7ee3-422c-8a6d-302fc22ffa92",
    "when": "20260204212249Z",
    "duration": "0.139987",
    "kw": {
      "key": "no_dna_range_defined",
      "range_start": 0,
      "range_max": 0,
      "next_start": 0,
      "next_max": 0,
      "msg": "No DNA range defined. If no masters define a range then users and groups cannot be created."
    }
  }
]


Reproducible: Always

Steps to Reproduce:
1. Start freeipa
2.
3.
Actual Results:
Produces errors as above

Expected Results:
Should start without errors