Bug 1684196
Summary: | Incorrect HREF in API for compliance result | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
Component: | API | Assignee: | Nick LaMuro <nlamuro> |
Status: | CLOSED ERRATA | QA Contact: | Parthvi Vala <pvala> |
Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
Priority: | high | ||
Version: | 5.9.6 | CC: | dmetzger, nlamuro, obarenbo, smallamp |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.9.9 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.9.9.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1682739 | Environment: | |
Last Closed: | 2019-03-19 07:22:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1682739 | ||
Bug Blocks: |
Comment 2
CFME Bot
2019-02-28 17:08:24 UTC
FIXED. Verified on 5.9.9.1.20190304164243_28a581b. 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" } ], ... } 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-2019:0600 |