api-ref: POST /flavors says that id is required but it's actually optional

Bug #1663389 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Matt Riedemann

Bug Description

The API reference docs for POST /flavors says that the 'id' field is required but it's actually optional according to the schema:

http://developer.openstack.org/api-ref/compute/?expanded=create-flavor-detail#create-flavor

id body string The ID of the flavor. While people often make this look like an int, this is really a string.

https://github.com/openstack/nova/blob/15.0.0.0rc1/nova/api/openstack/compute/schemas/flavor_manage.py#L30

If it's not provided, we default to generate a uuid:

https://github.com/openstack/nova/blob/15.0.0.0rc1/nova/compute/flavors.py#L74

Matt Riedemann (mriedem)
Changed in nova:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Matt Riedemann (mriedem)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/431747
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f7d9e82a2061c0d61b658265d1f871a0559c21b0
Submitter: Jenkins
Branch: master

commit f7d9e82a2061c0d61b658265d1f871a0559c21b0
Author: Matt Riedemann <email address hidden>
Date: Thu Feb 9 16:32:24 2017 -0500

    api-ref: mark id as optional in POST /flavors

    When creating a flavor you do not actually have to
    provide an id. If one is not provided in the request,
    an id is automatically generated from a uuid when
    creating the flavor. This updates the api-ref to
    point that out.

    Change-Id: Ie3c7042bd5f1ae05ad4e4eeba078f82c5e23d33a
    Closes-Bug: #1663389

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

This issue was fixed in the openstack/nova 16.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.