Improper relationships between parent and child shares using LVM driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Valeriy Ponomaryov |
Bug 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.
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://
[2] https:/
[3] https:/
[4] https:/
Changed in manila: | |
importance: | Undecided → Medium |
milestone: | none → ocata-2 |
description: | updated |
tags: | added: driver lvm |
description: | updated |
description: | updated |
Looks like it is caused by following bug: https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1071733
Local testing shows that local filesystems work ok, they do not overlap anyhow. But mounting them as NFS shares makes them refer to one single volume.