database backup not skipping the mentioned key space

Bug #1556353 reported by Vinoth Kannan Ganapathy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.22.x
Fix Committed
High
aswani kumar
R3.0
Fix Committed
High
aswani kumar
Trunk
Fix Committed
High
aswani kumar

Bug Description

Used fab backup/restore with build 2724, using key_space to skip analytics data backup.
Couple of issue here.

1. gave ContrailAnalytics in skip_keyspace , but the folder named as ContrailAnalyticsCql in 3.0, so the following proc
returns Cql and eventually fails to skip analytics backup

< def replace_key(text, skip_key):
< for key in skip_key:
< text = text.replace(key, “")

 Instead of giving the specific name in the skip_keyspace , can we have generic name that customer can understand and map it internally to the set of databases.
For example , instead expecting to give ContrailAnalyticsCql in the key_space, just ContrailAnalytics

2. It assumes the database having the snapshots dir are eligible for the backup instead of checking against the skip_keyspace.
if there is snapshots already taken, but would like to skip while backing up, it fails to do so.

        snapshot_dirs = sudo("find %s/ -name 'snapshots' " % db_path)
        snapshot_dirs = snapshot_dirs.split('\r\n')
        #get relative path to cassandra from db_path
        path_to_cassandra = re.search('.*/cassandra/',db_path).group(0)
        for snapshot_dir in snapshot_dirs:
            snapshot_list.append(snapshot_dir.replace(path_to_cassandra,'’))

Tags: provisioning
Revision history for this message
aswani kumar (aswanikumar90) wrote :

fix comitted

Jeba Paulaiyan (jebap)
information type: Proprietary → Public
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.