| 2016-11-29 15:17:52 |
Valeriy Ponomaryov |
bug |
|
|
added bug |
| 2016-11-29 15:17:58 |
Valeriy Ponomaryov |
manila: importance |
Undecided |
Medium |
|
| 2016-11-29 15:18:02 |
Valeriy Ponomaryov |
manila: milestone |
|
ocata-2 |
|
| 2016-11-29 15:19:06 |
Valeriy Ponomaryov |
description |
LVM driver has improper relationships between parent and child shares:
Steps to reproduce:
1) Create "parent" share.
2) Provide access to "parent" share (1) for some client machine and mount it there.
3) Create "file1" on "parent" share (1).
4) Create snapshot from "parent" share (1).
5) Create "file2" on "parent" share (1).
6) Create "child" share from "parent" share (1).
7) Provide access to "child" share (6) for some client machine and mount it there.
8) Create "file3" on "child" share (6).
9) List files of parent share.
Expected result: parent share has "file1" and "file2" files and child share has "file1" and "file3" files only.
Actual result: we see file in parent share that has just been created on child share and do not see file created on parent share after creation of a snapshot.
[1] http://logs.openstack.org/04/402604/3/check/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/92568c9/logs/testr_results.html.gz
[2] https://review.openstack.org/#/c/400758
[3] https://review.openstack.org/#/c/402404
[4] https://review.openstack.org/#/c/402604 |
LVM driver has improper relationships between parent and child shares:
Steps to reproduce:
1) Create "parent" share.
2) Provide access to "parent" share (1) for some client machine and mount it there.
3) Create "file1" on "parent" share (1).
4) Create snapshot from "parent" share (1).
5) Create "file2" on "parent" share (1).
6) Create "child" share from "parent" share (1).
7) Provide access to "child" share (6) for some client machine and mount it there.
8) Create "file3" on "child" share (6).
9) List files of parent share.
Expected result: parent share has "file1" and "file2" files and child share has "file1" and "file3" files only.
Actual result: we see "file3" in "parent" share that has just been created on "child" share and do not see "file2" created on parent share after creation of the snapshot.
[1] http://logs.openstack.org/04/402604/3/check/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/92568c9/logs/testr_results.html.gz
[2] https://review.openstack.org/#/c/400758
[3] https://review.openstack.org/#/c/402404
[4] https://review.openstack.org/#/c/402604 |
|
| 2016-11-29 15:19:13 |
Valeriy Ponomaryov |
tags |
|
driver lvm |
|
| 2016-11-29 15:19:48 |
Valeriy Ponomaryov |
description |
LVM driver has improper relationships between parent and child shares:
Steps to reproduce:
1) Create "parent" share.
2) Provide access to "parent" share (1) for some client machine and mount it there.
3) Create "file1" on "parent" share (1).
4) Create snapshot from "parent" share (1).
5) Create "file2" on "parent" share (1).
6) Create "child" share from "parent" share (1).
7) Provide access to "child" share (6) for some client machine and mount it there.
8) Create "file3" on "child" share (6).
9) List files of parent share.
Expected result: parent share has "file1" and "file2" files and child share has "file1" and "file3" files only.
Actual result: we see "file3" in "parent" share that has just been created on "child" share and do not see "file2" created on parent share after creation of the snapshot.
[1] http://logs.openstack.org/04/402604/3/check/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/92568c9/logs/testr_results.html.gz
[2] https://review.openstack.org/#/c/400758
[3] https://review.openstack.org/#/c/402404
[4] https://review.openstack.org/#/c/402604 |
LVM driver has improper relationships between parent and child shares:
Steps to reproduce:
1) Create "parent" share.
2) Provide access to "parent" share (1) for some client machine and mount it there.
3) Create "file1" on "parent" share (1).
4) Create snapshot from "parent" share (1).
5) Create "file2" on "parent" share (1).
6) Create "child" share from "parent" share (1).
7) Provide access to "child" share (6) for some client machine and mount it there.
8) Create "file3" on "child" share (6).
9) List files of parent share.
Expected result: parent share has "file1" and "file2" files and child share has "file1" and "file3" files only.
Actual result: we see "file3" in "parent" share that has just been created on "child" share and do not see "file2" created on parent share after creation of the snapshot.
Generic driver has the same problem using Cinder as backend with LVM driver enabled for it.
[1] http://logs.openstack.org/04/402604/3/check/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/92568c9/logs/testr_results.html.gz
[2] https://review.openstack.org/#/c/400758
[3] https://review.openstack.org/#/c/402404
[4] https://review.openstack.org/#/c/402604 |
|
| 2016-11-29 15:21:28 |
Valeriy Ponomaryov |
description |
LVM driver has improper relationships between parent and child shares:
Steps to reproduce:
1) Create "parent" share.
2) Provide access to "parent" share (1) for some client machine and mount it there.
3) Create "file1" on "parent" share (1).
4) Create snapshot from "parent" share (1).
5) Create "file2" on "parent" share (1).
6) Create "child" share from "parent" share (1).
7) Provide access to "child" share (6) for some client machine and mount it there.
8) Create "file3" on "child" share (6).
9) List files of parent share.
Expected result: parent share has "file1" and "file2" files and child share has "file1" and "file3" files only.
Actual result: we see "file3" in "parent" share that has just been created on "child" share and do not see "file2" created on parent share after creation of the snapshot.
Generic driver has the same problem using Cinder as backend with LVM driver enabled for it.
[1] http://logs.openstack.org/04/402604/3/check/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/92568c9/logs/testr_results.html.gz
[2] https://review.openstack.org/#/c/400758
[3] https://review.openstack.org/#/c/402404
[4] https://review.openstack.org/#/c/402604 |
LVM driver has improper relationships between parent and child shares:
Steps to reproduce:
1) Create "parent" share.
2) Provide access to "parent" share (1) for some client machine and mount it there.
3) Create "file1" on "parent" share (1).
4) Create snapshot from "parent" share (1).
5) Create "file2" on "parent" share (1).
6) Create "child" share from "parent" share (1).
7) Provide access to "child" share (6) for some client machine and mount it there.
8) Create "file3" on "child" share (6).
9) List files of parent share.
Expected result: parent share has "file1" and "file2" files and child share has "file1" and "file3" files only.
Actual result: we see "file3" in "parent" share that has just been created on "child" share and do not see "file2" created on parent share after creation of the snapshot.
Bug has been reproduced [1] in CI using [2], [3] and [4] changes that add/enable scenario tests for LVM driver.
Generic driver has the same problem using Cinder as backend with LVM driver enabled for it.
[1] http://logs.openstack.org/04/402604/3/check/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/92568c9/logs/testr_results.html.gz
[2] https://review.openstack.org/#/c/400758
[3] https://review.openstack.org/#/c/402404
[4] https://review.openstack.org/#/c/402604 |
|
| 2016-12-06 11:36:50 |
OpenStack Infra |
manila: status |
New |
In Progress |
|
| 2016-12-06 11:36:50 |
OpenStack Infra |
manila: assignee |
|
Valeriy Ponomaryov (vponomaryov) |
|
| 2016-12-09 20:20:21 |
OpenStack Infra |
manila: status |
In Progress |
Fix Released |
|
| 2019-02-18 10:33:43 |
OpenStack Infra |
tags |
driver lvm |
driver in-stable-rocky lvm |
|
| 2019-02-18 20:39:01 |
OpenStack Infra |
tags |
driver in-stable-rocky lvm |
driver in-stable-queens in-stable-rocky lvm |
|
