Steps to replicate the issue (include links if applicable):
What happens?:
At least one Trove VM did not resume correctly when all hypervisors were shut down and restarted during T329535 (as reported in T329853).
What should have happened instead?:
Trove VMs that were running before the restart should be restarted automatically,
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | BUG REPORT | Andrew | T329949 [Cloud VPS] Trove dbs do not restart after a hypervisor restart | ||
| Resolved | BUG REPORT | taavi | T329853 Trove database vanished |
I created an upstream bug for this: https://storyboard.openstack.org/#!/story/2010599
At least one Trove VM did not resume correctly when all hypervisors were shut down and restarted
In case it's useful to know, this affected the libup-db02 database VM (T329986).
This seems to have been fixed by upstream (although not the way I was going to fix it.) DB instances briefly display 'unknown' and 'error' state but eventually get back around to 'healthy'.