Bug 866934
| Summary: | API:Links given for the provider_accounts are not working while listing all provider_accounts via API | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | pushpesh sharma <psharma> | ||||
| Component: | aeolus-conductor | Assignee: | Richard Su <rwsu> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Rehana <aeolus-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 1.1.0 | CC: | bbandari, dajohnso, morazi | ||||
| Target Milestone: | beta6 | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-10-19 18:08:48 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
pushpesh sharma
2012-10-16 11:02:38 UTC
Created attachment 628105 [details]
provider accounts links
The links listed by the API are correct for version 1.1. Currently https://localhost/conductor/api/provider/id/provider_accounts/id is not implemented, but http://localhost/conductor/api/provider_accounts/id is. The resources are organized differently in the UI and is the reverse of the API. https://localhost/conductor/api/provider/id/provider_accounts/id is implemented, but http://localhost/conductor/api/provider_accounts/id is not. If you're are viewing the API from the browser you'll need to indicate the Accept header should be "application/xml", otherwise you'll see the UI try to present an html response that doesn't exist. From a browser, http://localhost/conductor/api/provider_accounts/id.xml would show the correct response from an API perspective. This does point to an interesting issue, whether requests are under http://localhost/conductor/api should default to respond as xml. Something worth considering for the next release. Reverting status change. I believe this is a consistency issue, pushpesh, correct me if I am wrong here... The problem is if I click on the any of the urls from the api responses like the following, I always get proper webpage but when the url is to a provider account, the screenshot error in comment 1 is displayed. https://localhost/conductor/api/pool_families/10 https://localhost/conductor/api/pools/10 https://localhost/conductor/api/provider/10 |