Red Hat Bugzilla – Bug 1206243
Api for available_clusters on vmware does not return expected value.
Last modified: 2016-07-27 05:14:52 EDT
Description of problem: I have a VMware cluster with the following setup Datacentername = nyc Clustername = nyccluster I have 2 hosts in the cluster and I am able to provision to it via sat6. When I try to query the vmware cluster information via api https://sat6.local.domb.com/api/v2/compute_resources/4/available_clusters I get back { "total": 4, "subtotal": 4, "page": 1, "per_page": 20, "search": null, "sort": { "by": null, "order": null }, "results": [{}] } This only happens with vmware. If I choose rhev it works https://sat6.local.domb.com/api/v2/compute_resources/3/available_clusters { "total": 4, "subtotal": 4, "page": 1, "per_page": 20, "search": null, "sort": { "by": null, "order": null }, "results": [{"name":"Default","id":"00000001-0001-0001-0001-00000000034c"}] } Version-Release number of selected component (if applicable): 6.0.8 How reproducible: Steps to Reproduce: 1. You need to have a vmware cluster :-) 2. Query the api of sat6 https://SAT6SERVER/api/v2/compute_resources/3/available_clusters Actual results: results hash is empty Expected results: results hash should contain vmware cluster Additional info:
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created redmine issue http://projects.theforeman.org/issues/9911 from this bug
Upstream bug component is Provisioning
Upstream bug component is Compute Resources
Fixed upstream for 1.10 under a different issue number, moving to post and updating the related issue.
Works for vmware cluster /api/v2/compute_resources/1/available_clusters Build: snap9.0 Output: { "total": 1, "subtotal": 1, "page": 1, "per_page": 20, "search": null, "sort": { "by": null, "order": null }, "results": [{"name":"CFME-ESX55-Cluster","id":"domain-c241","full_path":"CFME-ESX55-Cluster"}] }
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/RHBA-2016:1501