summaryrefslogtreecommitdiffstats
path: root/glustolibs-gluster/glustolibs/gluster/shared_storage_ops.py
diff options
context:
space:
mode:
authorkshithijiyer <kshithij.ki@gmail.com>2019-12-17 11:49:26 +0530
committerBala Konda Reddy M <bmekala@redhat.com>2020-01-16 06:23:19 +0000
commitd0aee85958ff13d15eaf75468fe9af0698b06f2e (patch)
treec45a072b5c261424fc268509b43f1c3ca23fa51e /glustolibs-gluster/glustolibs/gluster/shared_storage_ops.py
parent86d16d2a98af540ba458721edc2ac8a530c01635 (diff)
[TC] Snapshot + glusterd: Status of snapshot after glusterd restart
Checking the status of snapshot informations before and after restarting glusterd. Test case: 1. Create volume 2. Create two snapshots with description 3. Check snapshot status informations with snapname, volume name and without snap name/volname. 4. Restart glusterd on all nodes 5. Follow step3 again and validate snapshot History of the patch: The testcase was failing in CentOS-ci due to bug [1], However this bug was defered for fix. Post updating the code with the workaround mentioned below, it was observed that glusterd restart was failing due to bug [2]. And now as the both the bugs are fixed this patch is safe to merge. Workaround: Now the only possible workaround for this is to modify the function get_snap_info_by_volname() to not use --xml option and directly run the command which will dump the output as string which can be directly used in the testcase. This modification in the library function will not impact any other testcase. Links: [1] https://bugzilla.redhat.com/show_bug.cgi?id=1590797 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1782200 Change-Id: I26ac0aaa5f6c8849fd9de41f506d6d13fc55e166 Co-authored-by: srivickynesh <sselvan@redhat.com> Signed-off-by: srivickynesh <sselvan@redhat.com> Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
Diffstat (limited to 'glustolibs-gluster/glustolibs/gluster/shared_storage_ops.py')
0 files changed, 0 insertions, 0 deletions