LVM driver not enforcing new size when creating share from snapshot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
In Progress
|
Medium
|
Unassigned |
Bug Description
Description
===========
The kubernetes project "cloud-
We could further add a tempest test that creates a share of size X, writes data to it, snapshots it and creates a new share of size X+Y with the snapshot. We'd check in the test if the share is sized X+Y as requested.
Steps to reproduce
==================
A chronological list of steps which will help reproduce the issue you hit:
* Setup manila with devstack and LVM driver:
* Create a share of size 1
* Mount share, write some data into it
* Snapshot the share
* Create a new share from the snapshot with size 2
* Mount new share, verify size
Expected result
===============
Manila (and the backend driver) enforce the new size as requested, rather than the size of the original snapshot when creating a share.
Actual result
=============
New size not enforced when using the LVM driver.
Environment
===========
1. Exact version of OpenStack Manila you are running: OpenStack Zed
2. Which storage backend did you use? LVM
Logs
==============
Test Failure log: https:/
df o/p with some instrumentation in the test: https:/
[1] https:/
[2] https:/
[3] https:/
tags: | added: driver |
Changed in manila: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Additional comment are at https:/ /meetings. opendev. org/meetings/ manila/ 2023/manila. 2023-06- 01-15.00. log.html