8b16911cc2
Currently galera and ovn require a coordinated restart across the controller node when certmonger determines the certificate for a node has expired and it needs to regenerate it. But right now, when the tripleo certmonger puppet module is called to assert to state of the certificates, it ends up regenerating new certificate unconditionally. So the galera and ovn get restarted on stack update, even when there is no need to. To mitigate these unecessary restarts, disable the post-action for now until we fix the behaviour of tripleo's certmonger puppet module. This has the side effect that services won't get restarted automatically if no stack update takes place until the certificate expiration date is reached. Related-Bug: #1906505 Change-Id: I17f1364932e43b8487515084e41b525e186888db |
||
---|---|---|
.. | ||
mysql-base.yaml | ||
mysql-client.yaml | ||
mysql-container-puppet.yaml | ||
mysql-pacemaker-puppet.yaml | ||
redis-base-puppet.yaml | ||
redis-container-puppet.yaml | ||
redis-pacemaker-puppet.yaml |