Comment 7 for bug 1849323
Revision history for this message
| Rodrigo Barbieri (rodrigo-barbieri2010) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
ok I just re-tested the "clear non-leader data" solution and I got mixed results. I triggered leader changes by stopping jujud vault service and pausing hacluster each vault unit.
1) for some reason, not every leader change triggered a change of tokens. So, in some instances, the leader did not broadcast anything (or it did and the clear method overwrote it really fast). This is still unclear to me.
2) My nova-compute got into status "Waiting" while changing leaders, as per #1, the old leader cleared relation data, and the new leader did not broadcast new tokens.
I avoided running refresh-secrets action, as this is something that operators shouldn't have to run manually to fix things.
It is clear that just "clearing non-leader data" introduces a few issues, as there are other gaps throughout the vault charm code that are not handled properly under those circumstances.