OpenStack Compute (nova)

Placement API reference: GET /traits query parameter starts_with should be startswith

Bug #1714283 reported by Eric Fried
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Eric Fried

Bug Description

In the Placement API reference, the GET /traits [1] query parameter 'name' says it accepts a key called 'starts_with'. The actual API accepts 'startswith' (no underscore).

[1] https://developer.openstack.org/api-ref/placement/#list-traits

Revision history for this message
Eric Fried (efried) wrote :

Sorry, opened the wrong bug.

Changed in nova:
status: New → Invalid
Revision history for this message
Eric Fried (efried) wrote :

Meh, since I opened it, might as well use it.

Changed in nova:
assignee: nobody → Eric Fried (efried)
status: Invalid → New
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/499682

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

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

commit 3c4843beaf2bc2bfe35dc4b1c913e674307d711f
Author: Eric Fried <email address hidden>
Date: Thu Aug 31 10:27:39 2017 -0500

    [placement] api-ref GET /traits name:startswith

    In the Placement API reference, the GET /traits [1] query parameter
    'name' says it accepts a key called 'starts_with'. The actual API
    accepts 'startswith' (no underscore).

    [1] https://developer.openstack.org/api-ref/placement/#list-traits

    Change-Id: I5a1fa51fc751f2492ae6aa2b38893a9e06a26ed1
    Closes-Bug: #1714283

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

This issue was fixed in the openstack/nova 17.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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