mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2025-02-25 18:55:28 -06:00
69bda6b440
ipa-server-upgrade fails when running the ipaload_cacrt plugin. The plugin finds all CA certificates in /etc/httpd/alias and uploads them in LDAP below cn=certificates,cn=ipa,cn=etc,$BASEDN. The issue happens because there is already an entry in LDAP for IPA CA, but with a different DN. The nickname in /etc/httpd/alias can differ from $DOMAIN IPA CA. To avoid the issue: 1/ during upgrade, run a new plugin that removes duplicates and restarts ldap (to make sure that uniqueness attr plugin is working after the new plugin) 2/ modify upload_cacert plugin so that it is using $DOMAIN IPA CA instead of cn=$nickname,cn=ipa,cn=etc,$BASEDN when uploading IPA CA. https://pagure.io/freeipa/issue/7125 Reviewed-By: Fraser Tweedale <ftweedal@redhat.com> |
||
|---|---|---|
| .. | ||
| 05-pre_upgrade_plugins.update | ||
| 10-config.update | ||
| 10-enable-betxn.update | ||
| 10-ipapwd.update | ||
| 10-rootdse.update | ||
| 10-selinuxusermap.update | ||
| 10-uniqueness.update | ||
| 19-managed-entries.update | ||
| 20-aci.update | ||
| 20-default_password_policy.update | ||
| 20-dna.update | ||
| 20-host_nis_groups.update | ||
| 20-idoverride_index.update | ||
| 20-indices.update | ||
| 20-ipaservers_hostgroup.update | ||
| 20-nss_ldap.update | ||
| 20-replication.update | ||
| 20-sslciphers.update | ||
| 20-syncrepl.update | ||
| 20-user_private_groups.update | ||
| 20-uuid.update | ||
| 20-winsync_index.update | ||
| 21-ca_renewal_container.update | ||
| 21-certstore_container.update | ||
| 21-replicas_container.update | ||
| 25-referint.update | ||
| 30-provisioning.update | ||
| 30-s4u2proxy.update | ||
| 37-locations.update | ||
| 40-automember.update | ||
| 40-certprofile.update | ||
| 40-delegation.update | ||
| 40-dns.update | ||
| 40-otp.update | ||
| 40-realm_domains.update | ||
| 40-replication.update | ||
| 40-vault.update | ||
| 41-caacl.update | ||
| 41-lightweight-cas.update | ||
| 45-roles.update | ||
| 50-7_bit_check.update | ||
| 50-dogtag10-migration.update | ||
| 50-externalmembers.update | ||
| 50-groupuuid.update | ||
| 50-hbacservice.update | ||
| 50-ipaconfig.update | ||
| 50-krbenctypes.update | ||
| 50-nis.update | ||
| 55-pbacmemberof.update | ||
| 59-trusts-sysacount.update | ||
| 60-trusts.update | ||
| 61-trusts-s4u2proxy.update | ||
| 62-ranges.update | ||
| 71-idviews-sasl-mapping.update | ||
| 71-idviews.update | ||
| 72-domainlevels.update | ||
| 73-certmap.update | ||
| 73-custodia.update | ||
| 73-winsync.update | ||
| 80-schema_compat.update | ||
| 90-post_upgrade_plugins.update | ||
| Makefile.am | ||
| README | ||
The update files are sorted before being processed because there are cases where order matters (such as getting schema added first, creating parent entries, etc). Updates are applied in blocks of ten so that any entries that are dependant on another can be added successfully without having to rely on the length of the DN to get the sorting correct. The file names should use the format #-<description>.update where # conforms to this: 10 - 19: Configuration 20 - 29: 389-ds configuration, new indices 30 - 39: Structual elements of the DIT 40 - 49: Pre-loaded data 50 - 59: Cleanup existing data 60 - 69: AD Trust 70 - 79: Reserved 80 - 89: Reserved These numbers aren't absolute, there may be reasons to put an update into one place or another, but by adhereing to the scheme it will be easier to find existing updates and know where to put new ones.