C02YK11RJHD4 sschultchen@C02YK11RJHD4:~$for i in 1 2 3; do for j in fra zrh nj va; do ssh root@ipa-${i}.prod.${j}.dc.linux.factset.com grep i-05bc65dc445905252 /var/log/httpd/error_log; echo root@ipa-${i}.prod.${j}.dc.linux.factset.com; done; done
we have some automation, that will put hosts into host groups, using the "hostgroup_add_member" RPC function.
we just found one case, where the call completed successfully, but the host did not actually make it into the hostgroup. here is the relevant log message:
apache error log: (on ipa-2.example.com) [Wed Mar 11 11:18:43.262333 2020] [:error] [pid 94481] ipa: INFO: [xmlserver_session] cwfm_aws.prod.us-east-1.aws@LINUX.EXAMPLE.COM: host_add(u'i-example-1.dev.us-east-1.aws.linux.example.com', random=1, setattr=(), force=1, version=u'2.51'): SUCCESS
(on ipa-1.example.com) [Wed Mar 11 11:18:49.008503 2020] [:error] [pid 75001] ipa: INFO: [jsonserver_session] awslambda@LINUX.EXAMPLE.COM: hostgroup_add_member(u'aws_micro_account_xxx', all=True, raw=False, version=u'2.231', no_members=False, host=u'i-example-1.dev.us-east-1.aws.linux.example.com'): SUCCESS
apache access log: x.x.x.x - awslambda@LINUX.EXAMPLE.COM [11/Mar/2020:11:18:48 -0400] "POST /ipa/session/json HTTP/1.1" 200 460
adding the host manually worked, also the automated process usually works.
is it maybe a timing issue, between creation of the host, and adding it to a host group? not sure but maybe ipa-2.example.com did not in time replicate the data of host creation to ipa-1.example.com, where the command hostgroup_add_member was executed.
host was not added to hostgroup
host is always added to hostgroup, or at least an error message should be created
[root@ipa-1.prod.va.dc httpd]$ rpm -q freeipa-server freeipa-client ipa-server ipa-client 389-ds-base pki-ca krb5-server package freeipa-server is not installed package freeipa-client is not installed ipa-server-4.6.5-11.el7_7.3.x86_64 ipa-client-4.6.5-11.el7_7.3.x86_64 389-ds-base-1.3.9.1-12.el7_7.x86_64 pki-ca-10.5.16-5.el7_7.noarch krb5-server-1.15.1-37.el7_7.2.x86_64
Metadata Update from @rcritten: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.