Bug 1184786
| Summary: | [RFE] Allow an attached volume to be extended | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eduard Barrera <ebarrera> | |
| Component: | openstack-nova | Assignee: | Lee Yarwood <lyarwood> | |
| Status: | CLOSED ERRATA | QA Contact: | James Parker <jparker> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 12.0 (Pike) | CC: | acanan, alonare, amodi, ccopello, cschwede, cshastri, dasmith, eelena, egallen, eglynn, eharney, gcharot, geguileo, igallagh, jamsmith, jhakimra, jparker, kchamart, lyarwood, mbooth, nchandek, nlevinki, sbauza, sclewis, scohen, sgordon, srevivo, vromanso | |
| Target Milestone: | Upstream M1 | Keywords: | FutureFeature, TestOnly, Triaged, ZStream | |
| Target Release: | 16.0 (Train on RHEL 8.1) | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| URL: | https://blueprints.launchpad.net/nova/+spec/nova-support-attached-volume-extend | |||
| Whiteboard: | upstream_milestone_none upstream_definition_approved upstream_status_needs-code-review | |||
| Fixed In Version: | openstack-nova-20.0.1-0.20191025043858.390db63.el8ost | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1634052 (view as bug list) | Environment: | ||
| Last Closed: | 2020-02-06 14:37:21 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1634052, 1689706, 1782452 | |||
Eric, Can you please take a look at this RFE with regards to https://blueprints.launchpad.net/cinder/+spec/inuse-extend-volume-extension & https://blueprints.launchpad.net/nova/+spec/online-volume-extend-extension and provide your feedback on the gaps? Thanks Sean (In reply to Sean Cohen from comment #3) Reviewing the material for this upstream, it looks like not much has progressed. The specs cover the basic requirements, but no code has been submitted yet. Steve,(In reply to Eric Harney from comment #4) > (In reply to Sean Cohen from comment #3) > > Reviewing the material for this upstream, it looks like not much has > progressed. The specs cover the basic requirements, but no code has been > submitted yet. Thanks Eric, indeed, that was my take as well, adding Steve for his 2 cents from Nova side.... (In reply to Sean Cohen from comment #5) > Steve,(In reply to Eric Harney from comment #4) > > (In reply to Sean Cohen from comment #3) > > > > Reviewing the material for this upstream, it looks like not much has > > progressed. The specs cover the basic requirements, but no code has been > > submitted yet. > > Thanks Eric, indeed, that was my take as well, adding Steve for his 2 cents > from Nova side.... There is no design specification attached to the Nova blueprint, so yeah. I would not expect any movement on this to be possible in Nova until such time as the outstanding issues on the Cinder blueprint are resolved. Specification was approved for Pike, but no code as yet. Pushing into our 13 potential bucket for consideration. Looks like this landed in nova in Pike (OSP12): https://review.openstack.org/#/c/454322/ For QE: Minimum testing needs to cover extending a cinder volume exposed to the compute host via NFS, iscsi, and Ceph. *** Bug 1698091 has been marked as a duplicate of this bug. *** *** Bug 1634052 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:0283 |
Description of problem: Currently cinder does not allow to extend volumes in different status than available so it requires to unmount the volume dettach and dettach it. /usr/lib/python2.7/site-packages/cinder/volume/api.py def extend(self, context, volume, new_size): if volume['status'] != 'available': <============================= msg = _('Volume status must be available to extend.') raise exception.InvalidVolume(reason=msg) size_increase = (int(new_size)) - volume['size'] if size_increase <= 0: msg = (_("New size for extend must be greater " "than current size. (current: %(size)s, " "extended: %(new_size)s)") % {'new_size': new_size, 'size': volume['size']}) raise exception.InvalidInput(reason=msg) try: reservations = QUOTAS.reserve(context, gigabytes=+size_increase) except exception.OverQuota as exc: usages = exc.kwargs['usages'] quotas = exc.kwargs['quotas'] We would like to be able to extend the volumes while they are attached