mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2025-01-11 00:31:56 -06:00
161008d5ca
ipactl is building a list of currently running services from the content of /var/run/ipa/services.list, and a list of expected services from the services configured in LDAP. Because CA and KRA both correspond to the same pki-tomcatd service, the lists may contain duplicates. The code handling these duplicates is called at the wrong place, and may result in a wrong list of services to stop / restart / start. The fix removes the duplicates before returning the lists, hence making sure that there is no error when building the list of services to stop / restart / start. Fixes: https://pagure.io/freeipa/issue/7927 Reviewed-By: Christian Heimes <cheimes@redhat.com> |
||
|---|---|---|
| .. | ||
| certmonger | ||
| custodia | ||
| html | ||
| migration | ||
| oddjob | ||
| restart_scripts | ||
| share | ||
| tools | ||
| ui | ||
| updates | ||
| wsgi | ||
| Makefile.am | ||
| README.schema | ||
Ground rules on adding new schema Brand new schema, particularly when written specifically for IPA, should be added in share/*.ldif. Any new files need to be explicitly loaded in ipaserver/install/dsinstance.py. These simply get copied directly into the new instance schema directory. Existing schema (e.g. in an LDAP draft) may either be added as a separate ldif in share or as an update in the updates directory. The advantage of adding the schema as an update is if 389-ds ever adds the schema then the installation won't fail due to existing schema failing to load during bootstrap. If the new schema requires a new container then this should be added to install/bootstrap-template.ldif.