| 2016-11-29 15:02:16 |
Valeriy Ponomaryov |
description |
ZFSonLinux share that was created from snapshot inherits access rules of a parent share. But it should not by design.
Steps to reproduce:
1) create "parent" share
2) add access rule to the "parent" (1) share
3) create snapshot from "parent" (1) share
4) create "child" share from snapshot (3)
Expected result: "child" share does not have access that was added to parent share
Actual result: "child" share does have access that was added to parent share
logs: http://logs.openstack.org/04/402604/3/check/gate-manila-tempest-dsvm-postgres-zfsonlinux-ubuntu-xenial-nv/a956ea7/logs/testr_results.html.gz
[1] https://review.openstack.org/#/c/400758
[2] https://review.openstack.org/#/c/402404
[3] https://review.openstack.org/#/c/402604 |
ZFSonLinux share that was created from snapshot inherits access rules of a parent share. But it should not by design.
Steps to reproduce:
1) create "parent" share
2) add access rule to the "parent" (1) share
3) create snapshot from "parent" (1) share
4) create "child" share from snapshot (3)
Expected result: "child" share does not have access that was added to parent share
Actual result: "child" share does have access that was added to parent share
It can be seen in logs of ZFSonLinux CI job that was reproduced with help of [1], [2] and [3] changes that add/enable scenario tests for this driver.
[1] http://logs.openstack.org/04/402604/3/check/gate-manila-tempest-dsvm-postgres-zfsonlinux-ubuntu-xenial-nv/a956ea7/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 |
|
