Bug 1682739 - Incorrect HREF in API for compliance result
Summary: Incorrect HREF in API for compliance result
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API
Version: 5.9.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.10.0
Assignee: Nick LaMuro
QA Contact: Parthvi Vala
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks: 1684196
TreeView+ depends on / blocked
 
Reported: 2019-02-25 18:41 UTC by Tuan
Modified: 2019-11-29 05:52 UTC (History)
4 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1684196 (view as bug list)
Environment:
Last Closed: 2019-03-26 21:02:58 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ManageIQ integration_tests pull 9694 0 'None' 'open' '[RFR] Audit qe-test-coverage for Customer BZs' 2019-11-29 05:52:22 UTC

Comment 4 dmetzger 2019-02-28 13:44:44 UTC
The specific fix for the incorrect HREF (https://github.com/ManageIQ/manageiq-api/pull/319) is being targeted for 5.9, the potential RFE request for a new API endpoint will be left to a new RFE BZ.

Comment 7 Parthvi Vala 2019-03-06 11:01:57 UTC
FIXED. Verified on 5.10.1.2.20190219165527_7a4a22b.

Steps taken to verify the BZ:
1. Create a compliance policy, and create a policy profile and assign the newly created compliance policy to it.
2. Assign the new policy profile to a VM.
3. Query the VM.
GET /api/vms/:id?attributes=compliances

Response: {
  "href": "https://<ip_address>/api/vms/8",
  "id": "8",
  "vendor": "vmware",
  "name": "v2v-rhel8-mini",
    ...
  "compliances": [
    {
      "id": "1",
      "resource_id": "8",
      "resource_type": "VmOrTemplate",
      "compliant": true,
      "timestamp": "2019-03-06T09:48:55Z",
      "updated_on": "2019-03-06T09:48:55Z",
      "event_type": "vm_compliance_check"
    }
  ],
    ...
}


Note You need to log in before you can comment on or make changes to this bug.