Hide Forgot
Description of problem: Enhance API to provide CloudVolumeTypes to support infrastructure mapping selection in support of OSP. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Upstream issue: https://github.com/ManageIQ/manageiq-api/issues/456
*** Bug 1623304 has been marked as a duplicate of this bug. ***
https://github.com/ManageIQ/manageiq/pull/17935
https://github.com/ManageIQ/manageiq-api/pull/465
New commit detected on ManageIQ/manageiq-api/master: https://github.com/ManageIQ/manageiq-api/commit/d41bc44497b8efe3118a7982173d452416f2ae9e commit d41bc44497b8efe3118a7982173d452416f2ae9e Author: James Wong <jwong@redhat.com> AuthorDate: Fri Aug 31 13:24:24 2018 -0400 Commit: James Wong <jwong@redhat.com> CommitDate: Fri Aug 31 13:24:24 2018 -0400 endpoint api/cloud_volume_types https://bugzilla.redhat.com/show_bug.cgi?id=1620228 app/controllers/api/cloud_volume_types_controller.rb | 3 + config/api.yml | 15 + spec/requests/cloud_volume_types_spec.rb | 48 + 3 files changed, 66 insertions(+)
Tested! When I do https://hostname/api/cloud_volume_types, I get following clean response - { "name": "cloud_volume_types", "count": 4, "subcount": 4, "pages": 1, "resources":[ { "href": "https://hostname/api/cloud_volume_types/1" }, { "href": "https://hostname/api/cloud_volume_types/2" }, { "href": "https://hostname/api/cloud_volume_types/3" }, { "href": "https://hostname/api/cloud_volume_types/4" } ], "links":{ "self": "https://hostname/api/cloud_volume_types?offset=0", "first": "https://hostname/api/cloud_volume_types?offset=0", "last": "https://hostname/api/cloud_volume_types?offset=0" } } Also tested same on manageiq's python api client, all works well. Verified on - 5.10.0.30.20181218191323_900a416
For QE's, we are in process to add its TCs to polarion https://github.com/ManageIQ/integration_tests/pull/8257/files is pending.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212