Cinder resize procedure should not require lock/unlock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Wei Zhou |
Bug Description
Brief Description
-----------------
The cinder resize procedure does not match what is documented. The current procedure requires a lock/unlock for some labs/disk types. The lock/unlock should not be required.
Severity
--------
Major
Steps to Reproduce
------------------
Currently to resize cinder successfully, the user must do the following:
1. On standby controller, lock controller, enlarge cinder partition and unlock
2. Swact
3. On new standby controller, lock controller, enlarge cinder partition and unlock
4. Swact
5. Now both cinder-volume sizes should be increased
In the documentation, cinder resize is described as an in-service procedure. No lock/unlock requirement is listed.
Expected Behavior
------------------
No lock/unlock required
Actual Behavior
----------------
Lock/unlock required with certain disks
Reproducibility
---------------
Reproducible
System Configuration
-------
Any LVM system with slower disks
Branch/Pull Time/Commit
-------
N/A
Timestamp/Logs
--------------
N/A
description: | updated |
Changed in starlingx: | |
importance: | Undecided → Medium |
status: | New → Triaged |
assignee: | nobody → Wei Zhou (wzhou007) |
tags: | added: stx.config |
tags: | added: stx.2019.03 |
tags: |
added: stx.2019.05 removed: stx.2019.03 |
tags: |
added: stx.2.0 removed: stx.2019.05 |
Fix proposed to branch: master /review. openstack. org/619051
Review: https:/