trove resize-volume for postgresql doesn't work, because its guest agent's stop_db def implementation doesn't have do_not_start_on_reboot optional argument
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
High
|
Nirav Shah |
Bug Description
With 'trove resize-volume <id>' for postgresql guest agent, I see:
2015-01-10 02:13:16.685 21358 ERROR trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
call
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
in call
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
2015-01-10 02:13:16.685 21358 TRACE trove.guestagen
This is because stop_db definition in guestagent/
def stop_db(self, context):
It should be similar to mysql's service.py implementation of stop_db:
def stop_db(self, update_db=False, do_not_
Changed in trove: | |
assignee: | nobody → Nirav Shah (nirav) |
Changed in trove: | |
status: | Confirmed → In Progress |
Changed in trove: | |
milestone: | kilo-2 → kilo-3 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | kilo-3 → 2015.1.0 |
Sound like a good catch. Unfortunately it's our fault because we don't have good test coverage for postgresql.
I will try int-tests for postgresql and will see if they are broken. But, any way, this is a real problem, thanks for pointing it out.