Volume extend broken in v2 API

Bug #1259552 reported by Jon Bernard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-cinderclient
Fix Released
Undecided
Jon Bernard

Bug Description

The volume extend operation using the v2 API fails with the following error:

    ERROR: 'Namespace' object has no attribute 'new_size'

This does not happen with v1 API.

Steps to reproduce:

  $ export OS_VOLUME_API_VERSION=2
  $ cinder create 1
  $ cinder extend <id> 2

Jon Bernard (jbernard)
Changed in python-cinderclient:
assignee: nobody → Jon Bernard (jbernard)
Changed in python-cinderclient:
status: New → In Progress
Revision history for this message
Rushi Agrawal (rushiagr) wrote :

Needs backport?

Revision history for this message
Jon Bernard (jbernard) wrote :

I would say yes, especially since it's a one-line patch. Are you suggesting I submit for stable/havana as well?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-cinderclient (master)

Reviewed: https://review.openstack.org/60965
Committed: https://git.openstack.org/cgit/openstack/python-cinderclient/commit/?id=c6a85e0c1c8226f5cfbf3dd92b4cd177fa3ee119
Submitter: Jenkins
Branch: master

commit c6a85e0c1c8226f5cfbf3dd92b4cd177fa3ee119
Author: Jon Bernard <email address hidden>
Date: Mon Dec 9 18:07:25 2013 -0500

    Fix broken argument name in v2 volume extend routine

    The new_size attribute was misspelled, causing the volume extend
    operation to fail with:

        ERROR: 'Namespace' object has no attribute 'new_size'

    This happens only with the v2 API, v1 works fine.

    Change-Id: Icb6b5008dad229f21e7906d9b5342d41f5e760cd
    Closes-Bug: #1259552

Changed in python-cinderclient:
status: In Progress → Fix Committed
Revision history for this message
John Griffith (john-griffith) wrote :

There's no concept of backports in cinderclient :)

You just pip install the latest version.

Changed in python-cinderclient:
milestone: none → 1.3.1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.