Cleanup MagnetoDB specific data from Cassandra

Bug #1374065 reported by Alexei Vinogradov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MagnetoDB
Fix Released
Medium
Alexei Vinogradov

Bug Description

When unstack.sh is executed it stops all the devstack processes but does not clean up MagnetoDB specific data from C*

When executed stack.sh after unstack.sh we have the following error:

/home/stack/.ccm/cql.txt:2:Bad Request: Cannot add existing keyspace "magnetodb"
/home/stack/.ccm/cql.txt:3:Bad Request: Cannot add existing keyspace "user_default_tenant"
/home/stack/.ccm/cql.txt:4:Bad Request: Cannot add existing keyspace "user_"
/home/stack/.ccm/cql.txt:5:Bad Request: Cannot add already existing column family "table_info" to keyspace "magnetodb"

Changed in magnetodb:
assignee: nobody → Alexei Vinogradov (spyray)
status: New → In Progress
Changed in magnetodb:
milestone: none → juno-rc1
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to magnetodb (master)

Reviewed: https://review.openstack.org/124078
Committed: https://git.openstack.org/cgit/stackforge/magnetodb/commit/?id=d325113ed1ccc1f579c707214acd5d8a24f01806
Submitter: Jenkins
Branch: master

commit d325113ed1ccc1f579c707214acd5d8a24f01806
Author: Alexei Vinogradov <email address hidden>
Date: Thu Sep 25 15:09:16 2014 +0000

    Cleanup MagnetoDB specific data from Cassandra

    When executed stack.sh after unstack.sh had errors with re-creation key-spaces

    Related-Bug: #1374065
    Change-Id: Ic540be67e2bd0745031d50da499231674036e1eb

Changed in magnetodb:
status: In Progress → Fix Committed
Changed in magnetodb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.