5eb01c517f
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
|
||
---|---|---|
.. | ||
README.rst | ||
ipaclient.yaml | ||
ipsec.yaml | ||
kubernetes-master.yaml | ||
kubernetes-worker.yaml | ||
openshift-cns.yaml | ||
openshift-infra.yaml | ||
openshift-master.yaml | ||
openshift-node.yaml | ||
openshift-worker.yaml | ||
rhsm.yaml | ||
skydive-agent.yaml | ||
skydive-analyzer.yaml |
README.rst
Externally Installed Services
The services in this directory and the Ansible hook they use (external_deploy_tasks) are currently considered experimental.