When we do backup for a volume, the backup notification is called
periodically, but if we do other operations (like retype operation)
in parallel, there is a possible to record the "volume.retype" and
"backup.createprogress".
This patch try to mock the send notification methods to ensure this
doesn't happen.
Reviewed: https:/ /review. openstack. org/627329 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=32ef92fa4bc 7b7db6df1c023b6 460fb25474b0f5
Committed: https:/
Submitter: Zuul
Branch: master
commit 32ef92fa4bc7b7d b6df1c023b6460f b25474b0f5
Author: Yikun Jiang <email address hidden>
Date: Wed Dec 26 10:58:13 2018 +0800
Fix retype notifier test case (BackupNFSTestCase)
When we do backup for a volume, the backup notification is called createprogress" .
periodically, but if we do other operations (like retype operation)
in parallel, there is a possible to record the "volume.retype" and
"backup.
This patch try to mock the send notification methods to ensure this
doesn't happen.
Change-Id: Iad899944b54a05 56ff0a946d18fcd b7e1680de69
Closes-Bug: #1803648