Ade Lee 5eb01c517f Restart certmnonger after registering system with IPA ... If certmonger is not restarted when the server is registered with IPA, then it may define the IPA CA as unreachable. This results in CA certs not being stored when cert requests are made with a -F option. Eventually, certmonger refreshes itself, but this can take up to 8 hours. We see this sometimes when doing brownfield deploys. The ca cert fails to be created for some requests, resulting in containers being unable to load. We fix this by simply restarting certmonger after enrollment, and avoiding the whole confused state. Closes-Bug: 1850647 Change-Id: Id968a2d5170af1485417e41318e0187d79cd4aae (cherry picked from commit bf0bc85ef4)		2019-10-30 14:25:29 +00:00
..
all_nodes	Change template names to rocky	2018-05-09 08:28:42 +02:00
nova_metadata/krb-service-principals	Per-Role krb-service-principal for CompactServices	2019-07-03 07:01:41 +00:00
post_deploy	Filter nameservers for undercloud networks	2019-08-29 15:17:14 +00:00
pre_deploy/rhel-registration	Fix usage of satellite in organization mode	2019-04-08 09:20:41 +02:00
pre_network	Fix for enable VFIO module on boot for SR-IOV deployments	2019-08-16 11:33:16 +02:00
services	Restart certmnonger after registering system with IPA	2019-10-30 14:25:29 +00:00
tasks	Merge "Python 3 compatibility: fix has_key"	2018-11-23 12:28:29 +00:00