| 2016-10-07 09:51:06 |
Valeriy Ponomaryov |
bug |
|
|
added bug |
| 2016-10-07 09:52:00 |
Valeriy Ponomaryov |
summary |
Concurrency of periodic replica update call and manual replica status update |
Tempest test "test_promote_out_of_sync_share_replica" is concurrency-prone |
|
| 2016-10-07 09:52:23 |
Valeriy Ponomaryov |
description |
Recently, in CI, was observed error in one of replication tests [1].
Where we do following:
1) Create share
2) Create replica
3) Reset state of replica to "out_of_sync"
4) Wait for updated "out_of_sync" status
5) Try to promote replica
And there is possible concurrency when between steps 3 and 4 we can get periodic replica update that occurred in case of observed error [1].
Proof:
Call of API comes first [2], then arrives periodic update [3] and tempest test tries to get updated status in [4].
[1] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/tempest_2/testr_results.html.gz
[2] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_42_938
[3] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-shr.txt.gz#_2016-10-07_05_55_43_046
[4] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_43_175 |
Recently, in CI, was observed error in one of replication tests [1].
Where we do following:
1) Create share
2) Create replica
3) Reset state of replica to "out_of_sync"
4) Wait for updated "out_of_sync" status
5) Try to promote replica
And there is possible concurrency between steps 3 and 4 we can get periodic replica update that occurred in case of observed error [1].
Proof:
Call of API comes first [2], then arrives periodic update [3] and tempest test tries to get updated status in [4].
[1] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/tempest_2/testr_results.html.gz
[2] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_42_938
[3] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-shr.txt.gz#_2016-10-07_05_55_43_046
[4] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_43_175 |
|
| 2016-10-07 09:52:32 |
Valeriy Ponomaryov |
description |
Recently, in CI, was observed error in one of replication tests [1].
Where we do following:
1) Create share
2) Create replica
3) Reset state of replica to "out_of_sync"
4) Wait for updated "out_of_sync" status
5) Try to promote replica
And there is possible concurrency between steps 3 and 4 we can get periodic replica update that occurred in case of observed error [1].
Proof:
Call of API comes first [2], then arrives periodic update [3] and tempest test tries to get updated status in [4].
[1] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/tempest_2/testr_results.html.gz
[2] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_42_938
[3] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-shr.txt.gz#_2016-10-07_05_55_43_046
[4] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_43_175 |
Recently, in CI, was observed error in one of replication tests [1].
Where we do following:
1) Create share
2) Create replica
3) Reset state of replica to "out_of_sync"
4) Wait for updated "out_of_sync" status
5) Try to promote replica
And there is possible concurrency between steps 3 and 4 when we can get periodic replica update that occurred in case of observed error [1].
Proof:
Call of API comes first [2], then arrives periodic update [3] and tempest test tries to get updated status in [4].
[1] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/tempest_2/testr_results.html.gz
[2] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_42_938
[3] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-shr.txt.gz#_2016-10-07_05_55_43_046
[4] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_43_175 |
|
| 2016-10-07 09:53:17 |
Valeriy Ponomaryov |
description |
Recently, in CI, was observed error in one of replication tests [1].
Where we do following:
1) Create share
2) Create replica
3) Reset state of replica to "out_of_sync"
4) Wait for updated "out_of_sync" status
5) Try to promote replica
And there is possible concurrency between steps 3 and 4 when we can get periodic replica update that occurred in case of observed error [1].
Proof:
Call of API comes first [2], then arrives periodic update [3] and tempest test tries to get updated status in [4].
[1] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/tempest_2/testr_results.html.gz
[2] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_42_938
[3] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-shr.txt.gz#_2016-10-07_05_55_43_046
[4] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_43_175 |
Recently, in CI, was observed error in one of replication tests [1].
Where we do following:
1) Create share
2) Create replica
3) Reset state of replica to "out_of_sync"
4) Wait for updated "out_of_sync" status
5) Try to promote replica
And there is possible concurrency between steps 3 and 4 when we can get periodic replica update that occurred in case of observed error [1].
Proof:
Call of API comes first [2], then arrives periodic update [3] and, finally, tempest test tries to get updated status in [4] and sees that it has "in_sync" status as was [1].
[1] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/tempest_2/testr_results.html.gz
[2] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_42_938
[3] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-shr.txt.gz#_2016-10-07_05_55_43_046
[4] http://logs.openstack.org/19/383119/2/check/gate-manila-tempest-minimal-dsvm-dummy-ubuntu-xenial-nv/9386587/logs/screen-m-api.txt.gz#_2016-10-07_05_55_43_175 |
|
| 2016-10-07 09:53:44 |
Valeriy Ponomaryov |
tags |
|
replication tempest |
|
| 2016-10-07 10:00:22 |
Valeriy Ponomaryov |
bug |
|
|
added subscriber Goutham Pacha Ravi |
| 2016-10-11 08:08:18 |
Valeriy Ponomaryov |
manila: importance |
Undecided |
High |
|
| 2016-10-11 12:47:55 |
Goutham Pacha Ravi |
manila: assignee |
|
Goutham Pacha Ravi (gouthamr) |
|
| 2016-10-11 12:47:58 |
Goutham Pacha Ravi |
manila: milestone |
|
ocata-1 |
|
| 2016-10-11 12:48:03 |
Goutham Pacha Ravi |
manila: status |
New |
Confirmed |
|
| 2017-01-18 15:21:19 |
Tom Barron |
bug |
|
|
added subscriber Tom Barron |
| 2018-03-16 14:12:08 |
Goutham Pacha Ravi |
manila: assignee |
Goutham Pacha Ravi (gouthamr) |
|
|
| 2018-03-16 14:12:12 |
Goutham Pacha Ravi |
manila: milestone |
ocata-1 |
|
|
| 2018-03-16 14:12:19 |
Goutham Pacha Ravi |
manila: importance |
High |
Medium |
|
| 2018-06-19 15:35:07 |
Tom Barron |
tags |
replication tempest |
races replication tempest |
|
| 2019-03-12 17:21:38 |
Goutham Pacha Ravi |
summary |
Tempest test "test_promote_out_of_sync_share_replica" is concurrency-prone |
Tempest tests "test_promote_out_of_sync_share_replica" and "test_resync_share_replica" are concurrency-prone |
|
| 2019-08-15 15:43:55 |
Jason Grosso |
manila: assignee |
|
Douglas Viroel (dviroel) |
|
| 2021-10-14 15:30:08 |
Goutham Pacha Ravi |
manila: assignee |
Douglas Viroel (dviroel) |
|
|
| 2021-10-14 15:31:23 |
Fábio Oliveira |
manila: assignee |
|
Fábio Oliveira (fabiooliveira1) |
|
| 2021-10-14 15:34:08 |
Vida Haririan |
manila: milestone |
|
yoga-1 |
|
| 2021-10-15 17:01:56 |
OpenStack Infra |
manila: status |
Confirmed |
In Progress |
|
| 2021-11-23 01:08:10 |
OpenStack Infra |
manila: status |
In Progress |
Fix Released |
|
