Bug 1420872

Summary: entities under /api/notifications collection are missing "delete" action with "DELETE" method
Product: Red Hat CloudForms Management Engine Reporter: Martin Kourim <mkourim>
Component: APIAssignee: Tim Wade <twade>
Status: CLOSED ERRATA QA Contact: Martin Kourim <mkourim>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.7.0CC: jhardy, obarenbo, simaishi, twade
Target Milestone: GA   
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: api:rest
Fixed In Version: 5.9.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-01 13:09:24 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 Martin Kourim 2017-02-09 17:24:42 UTC 
Description of problem:
Entities under /api/notifications collection have "delete" action with "POST" method available, but unlike entities in other collections (e.g. service_dialogs, blueprints, ...) they are missing "delete" action with "DELETE" method.


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


How reproducible:
100%


Steps to Reproduce:
1. create notifications (e.g. with automation request, provosioning requests, ...)
2. check under /api/notifications/:id that there is not "delete" action with "DELETE" method available
Comment 2 Tim Wade 2017-06-27 16:27:02 UTC 
PR: https://github.com/ManageIQ/manageiq/pull/14775
Comment 3 Martin Kourim 2017-10-13 13:13:52 UTC 
Verified on 5.9.0.1 that resources under /api/notifications collection have "delete" action with "DELETE" method available.
Comment 6 errata-xmlrpc 2018-03-01 13:09:24 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