Russ Long via FreeIPA-users wrote: > Hello, > > I have an automember rule for a hostgroup where it uses the nshostlocation of > the host to then add the host to the group. When adding new hosts, which are > installed via ipa-client-install, and then have the nshostlocation added via > ipa host-mod, all in an automated process, the new hosts are not being added > to the group. If I run an automembership rebuild, the hosts are then added. > > As these hosts spin up and down frequently, having to manually trigger this > is less than ideal. Is there a better way to handle this? I'm not dead set > on using the nshostlocation for the automember rule, but it seemed the > easiest and most appropriate for my situation.
What version of 389-ds-base are you running? 389 made a change in 1.4.0.21+ where modify operations also trigger a rebuild. rob _______________________________________________ FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
