When doing Live migration with shared storage, it happens erratically,
that the check for the shared storage test_file fails. Because the shared
volume is under heavy IO (many instances on many compute nodes) the client
does not immediately sees the new content of the folder. This delay
could take up to 30s.
This can be fixed if the client is forced to refresh the directories
content, which can be achieved by 'touch' on the directory. Doing so,
the test_file is visibile instantly, within ms.
The patch adds a 'touch' on instances_path in check_shared_storage_test_file,
before checking the existence of the file.
Reviewed: https:/ /review. openstack. org/382159 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=eeb23c78914 891a5a6943c09c8 7aceb720d45f58
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit eeb23c78914891a 5a6943c09c87ace b720d45f58
Author: Tom Patzig <email address hidden>
Date: Wed Sep 7 11:16:49 2016 +0200
refresh instances_path when shared storage used
When doing Live migration with shared storage, it happens erratically, storage_ test_file,
that the check for the shared storage test_file fails. Because the shared
volume is under heavy IO (many instances on many compute nodes) the client
does not immediately sees the new content of the folder. This delay
could take up to 30s.
This can be fixed if the client is forced to refresh the directories
content, which can be achieved by 'touch' on the directory. Doing so,
the test_file is visibile instantly, within ms.
The patch adds a 'touch' on instances_path in check_shared_
before checking the existence of the file.
Conflicts:
nova/tests/ unit/virt/ libvirt/ test_driver. py
NOTE(lyarwood): Conflict caused by the signature of shared_ storage_ test_file changing as part of I6cca257
_check_
Change-Id: I16be3914227851 7f43e6eca3441a5 6cbc9561113 b3cce77d9431692 2496bbaf9a)
Closes-Bug: #1617299
(cherry picked from commit 1af73d1fb3169c5