Bug 1351733
| Summary: | APIDoc incorrect for accessing bootdisks | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | ckyriaki |
| Component: | Bootdisk Plugin | Assignee: | Swapnil Abnave <sabnave> |
| Status: | CLOSED ERRATA | QA Contact: | Bruno Rocha <rochacbruno> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.1.8 | CC: | abalakht, bbuckingham, kabbott, mmccune, rochacbruno, sabnave, stbenjam, sthirugn |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-21 16:32:26 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: | |||
|
Description
ckyriaki
2016-06-30 16:55:30 UTC
It's actually the API documentation generated inside of Satellite at /apidoc, so I think this belongs in the Bootdisk category - something in either the bootdisk plugin or Apipie needs fixing. Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17552 has been resolved. Using:
satellite-6.3.0-22.0.el7sat.noarch
Results:
The JSON in /apidoc/v2/disks/host.json still shows
"api_url":"/bootdisk/api/hosts/:host_id"
The HTML in /apidoc/v2/disks/host.html still shows
`GET /bootdisk/api/hosts/:host_id`
However, checking the PR https://github.com/theforeman/foreman_bootdisk/pull/34 I see that now `v2` is the default route (otherwise can be passed as a header).
I tested `/bootdisk/api/hosts/1` and got the same results as in `/bootdisk/api/v2/hosts/`
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-2018:0336 |