HA: galera and ovn-dbs are needlessly restarted at each stack update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Confirmed
|
Medium
|
Damien Ciabrini |
Bug Description
With [1] we introduced coordinated restart of HA resources across the
pacemaker cluster nodes, for resource like galera and ovn-dbs that
don't support reloading their certificate when a new one is being
issued.
However we're seeing that on every stack update - even noop ones -
when the tripleo certmonger puppet module is called to assert to
state of the certificates, it ends up regenerating new certificate
unconditionally, even if the old ones aren't expired.
Dec 2 10:10:10 database-0 puppet-
Dec 2 10:10:10 database-0 certmonger[29459]: 2020-12-02 10:10:10 [117460] Setting "CERTMONGER_
Dec 2 10:10:10 database-0 certmonger[29459]: 2020-12-02 10:10:10 [117460] Setting "CERTMONGER_
Dec 2 10:10:10 database-0 certmonger[29459]: database-
Dec 2 10:10:10 database-0 certmonger[29459]: 2020-12-02 10:10:10 [117460] Setting "CERTMONGER_
Dec 2 10:10:10 database-0 certmonger[29459]: 2020-12-02 10:10:10 [117460] Setting "CERTMONGER_
This in turns restarts galera and ovn on every stack update, even
when that is not needed.
[1] Ib2b62e33b34cf7
Changed in tripleo: | |
milestone: | wallaby-1 → wallaby-2 |
Changed in tripleo: | |
milestone: | wallaby-2 → wallaby-3 |
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
Changed in tripleo: | |
milestone: | xena-2 → xena-3 |
Change abandoned by "Damien Ciabrini <email address hidden>" on branch: master /review. opendev. org/c/openstack /puppet- tripleo/ +/771227
Review: https:/
Reason: certs are now managed in ansible, so let's drop that