Manila share does not get into "shrinking_possible_data_loss_error" status when shrinking a share
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Low
|
Daniel Tapia |
Bug Description
Description of problem:
Manila share does not get into "shrinking_
status when shrinking a share which will cause to lose a data.
Version-Release number of selected component (if applicable):
puppet-
python2-
python2-
How reproducible:
100%
Steps to Reproduce:
1. Launch an instance
2. Create share (Configured size + 1)
3. Configure RW access to the share
4. Perform ssh to instance
5. Mount share
6. Write data in share (in excess of 1GB)
7. Shrink share to 1GB
Actual results:
Manila share get into "shrinking_error" status.
Expected results:
Manila share should get into "shrinking_
Additional info:
2020-01-05 06:27:14.166 43 ERROR oslo_messaging.
2020-01-05 06:27:14.166 43 ERROR oslo_messaging.
2020-01-05 06:27:14.166 43 ERROR oslo_messaging.
2020-01-05 06:27:14.166 43 ERROR oslo_messaging.
2020-01-05 06:27:14.166 43 ERROR oslo_messaging.
e to set volume attribute "size" for volume "share_
2020-01-05 06:27:14.166 43 ERROR oslo_messaging.
Traceback (most recent call last):
File "/home/
LOG.debug('Step 8 - try update size, shrink and wait')
File "/home/
"shares/
File "/home/
headers=
File "tempest/
return self.request(
File "tempest/
self.
File "tempest/
raise exceptions.
tempest.
Details: {u'message': u'Invalid share: Share 15888b1a-
tags: | added: drivers netapp |
Changed in manila: | |
importance: | Undecided → Low |
assignee: | nobody → Douglas Viroel (dviroel) |
status: | New → Triaged |
Changed in manila: | |
milestone: | none → ussuri-3 |
status: | Triaged → Confirmed |
Changed in manila: | |
assignee: | Douglas Viroel (dviroel) → Daniel Tapia (danielarthurt) |
Changed in manila: | |
milestone: | ussuri-3 → ussuri-rc1 |
I think the status of the share should remain "available" and not stuck on "shrinking_error".
I suggest throwing a message to the user that indicate the shrinking failed, something like:
"The shrinking attempt was rejected due to insufficient size"