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.
Thanks, Russ
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
That appears to likely be the issue. I am running 1.3.10.2-9.el7_9 currently, and as I'm on CentOS 7.9, the latest available is only 1.3.10.2-10.el7_9.
Is there a way that I'm missing to set the location as part of the ipa-client-install, and therefore avoiding this issue?
--Russ
Russ Long via FreeIPA-users wrote:
That appears to likely be the issue. I am running 1.3.10.2-9.el7_9 currently, and as I'm on CentOS 7.9, the latest available is only 1.3.10.2-10.el7_9.
Is there a way that I'm missing to set the location as part of the ipa-client-install, and therefore avoiding this issue?
Sorry, there is no way to pass this during client install. The rebuild takes options to limit the scope of the process if that helps.
rob
freeipa-users@lists.fedorahosted.org