commit | 126f5a1557b555c13905f52ff728b9f526d3b5e1 | [log] [tgz] |
---|---|---|
author | jeremy.zhang <zhangjun_inspur@163.com> | Thu Aug 24 10:40:26 2017 +0800 |
committer | Jeremy Zhang <zhangjun_inspur@163.com> | Thu Aug 31 14:45:23 2017 +0000 |
tree | f1bbdb098a5aa2b3c8bd9f87c94e056b541fc3cf | |
parent | 6eb7d2e59bcc939492b29bd10832435ea217b64c [diff] |
Fix for resetting snapshot status Reset snapshot status API is a snapshot action and its return code is 202, which means it is not a sync procedure. Although the API is mainly a DB operation and the snapshot status will be changed quickly, it is not stable to verify the snapshot status immediately after calling the API. It is more suitable to use 'waiters' function to wait for the snapshot status to be changed. Change-Id: I6e954e60b5318dd1271afcbf124a7b03584dc84a