The "parent_provider_uuid" response parameter for resource provider create/list/show/update is missing the 1.14 min_version flag

[Matt Riedemann]

This was unintentionally regressed here:

https://review.openstack.org/#/c/548934/5/placement-api-ref/source/parameters.yaml@354

[OpenStack Infra (hudson-openstack)]

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

[Matt Riedemann (mriedem)]

Correction, parent_provider_uuid was always in the POST /resource_providers response which started returning a body in 1.20.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/579577
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d1bc821ee6b2eb15613bb4f58fbec84946f3511c
Submitter: Zuul
Branch: master

commit d1bc821ee6b2eb15613bb4f58fbec84946f3511c
Author: Matt Riedemann <email address hidden>
Date: Mon Jul 2 10:38:28 2018 -0400

    api-ref: fix min_version for parent_provider_uuid in responses

    Due to a regression in I8624e194fe0173531c5aa2119c903e3c68b8c6cd, the
    min_version on the parent_provider_uuid response parameter was missing
    and is added back here. For sanity reasons, the variables are renamed
    and substitution anchor usage is dropped.

    To recap the microversions:

    1.14
    ----

    parent_provider_uuid and root_provider_uuid were added to the
    responses for:

    * GET /resource_providers (list)
    * GET /resource_providers/{uuid} (show)
    * PUT /resource_providers/{uuid} (update)

    parent_provider_uuid was added to the request for:

    * POST /resource_providers (create)
    * PUT /resource_providers/{uuid} (update)

    1.20
    ----

    We started returning a response body from
    POST /resource_providers (create) which included
    parent_provider_uuid and root_provider_uuid but the parameters
    are not versioned in that case since the entire response is
    versioned for 1.20.

    Change-Id: I6c9a1072fa2a59e408472f1a4b52b3a8c6a9b343
    Closes-Bug: #1779700

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/nova 18.0.0.0rc1 release candidate.