Bug 1485310 - href_slug attribute pointing to wrong collection
Summary: href_slug attribute pointing to wrong collection
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.9.0
Assignee: Jillian Tullo
QA Contact: Martin Kourim
URL:
Whiteboard: api:rest
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-25 11:16 UTC by Martin Kourim
Modified: 2018-03-14 15:00 UTC (History)
6 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-01 13:15:53 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 0 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 18:37:12 UTC

Description Martin Kourim 2017-08-25 11:16:00 UTC 
Description of problem:
In case of resources in the "policy_actions" and "automate_domains" collections the "href_slug" attribute points to wrong collections ("actions" and "automate" respectively).

Version-Release number of selected component (if applicable):
5.8.1.5


How reproducible:
very


Steps to Reproduce:
1. GET /api/policy_actions?expand=resources&attributes=href_slug
2. GET /api/automate_domains?expand=resources&attributes=href_slug
Comment 2 Dave Johnson 2017-09-18 16:59:35 UTC 
Martin, same here, any impact on automation?  If so, please add PrioBumpQA keyword.
Comment 3 Jillian Tullo 2017-10-03 13:30:54 UTC 
PR: https://github.com/ManageIQ/manageiq-api/pull/86
Comment 4 Martin Kourim 2017-10-18 21:02:39 UTC 
Verified that in the "policy_actions" and "automate_domains" collections the "href_slug" attribute points to correct collection.
Comment 7 errata-xmlrpc 2018-03-01 13:15:53 UTC 
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:0380
Note You need to log in before you can comment on or make changes to this bug.