reset-group-snalshot api-ref not correct for 'status' attribute

Bug #1719930 reported by Ghanshyam Mann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Ghanshyam Mann

Bug Description

reset-group-snalshot api-ref not correct for 'status' attribute. That is mentioned as optional for request.
'status' in API request is mandatory attribute.

Also 'project_id' is mentioned as body element instead of path.

Those are confusing while implementing tests for this API - https://review.openstack.org/#/c/495735/
https://developer.openstack.org/api-ref/block-storage/v3/#reset-group-snapshot-status

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/507892

Changed in cinder:
assignee: nobody → Ghanshyam Mann (ghanshyammann)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/507892
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=ea3603c24564cf5990b96b2736e8285048df78e9
Submitter: Jenkins
Branch: master

commit ea3603c24564cf5990b96b2736e8285048df78e9
Author: ghanshyam <email address hidden>
Date: Wed Sep 27 15:10:37 2017 +0000

    Fix api-ref for reset group snapshot

    reset-group-snalshot api-ref not correct for 'status' attribute.
    That is mentioned as optional for request.
    'status' in API request is mandatory attribute.

    Also 'project_id' is mentioned as body element instead of path.

    Those are confusing while implementing tests for this API
     - https://review.openstack.org/#/c/495735/
    https://developer.openstack.org/api-ref/block-storage/v3/#reset-group-snapshot-status
    Closes-Bug: #1719930

    Change-Id: Id2016f86d0eae60d96df7a12eda1bbec9d1129a8

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 12.0.0.0b1

This issue was fixed in the openstack/cinder 12.0.0.0b1 development milestone.

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.