Vertica instances go to SHUTDOWN before going ACTIVE
Bug #1487233 reported by
Sharika
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Peter Stachowski |
Bug Description
When setting up a Vertica cluster, the guest agent gets install_cluster message much later than the _get_db_status. The _get_db_status causes the Vertica instances to go to SHUTDOWN because the heartbeat message tries to access a file that does not exist yet on the instance. Therefore instances in cluster go BUILD --> SHUTDOWN --> BUILD --> ACTIVE.
Changed in trove: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/215387
Review: https:/