Bug 1645062 - host_collection controller responds with 200 instead of 201 to a POST request
Summary: host_collection controller responds with 200 instead of 201 to a POST request
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Collections
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: Swetha Seelam
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-01 10:45 UTC by Roman Plevka
Modified: 2020-10-27 12:58 UTC (History)
4 users (show)

Fixed In Version: tfm-rubygem-katello-3.15.0-0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:57:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 28219 0 Normal Closed repositories controller responds with 200 instead of 201 to a POST request 2020-10-28 17:15:27 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 12:58:18 UTC

Description Roman Plevka 2018-11-01 10:45:05 UTC
Description of problem:
This is already known and closed upstream (https://projects.theforeman.org/issues/23497) but i'm opening a brand new bug here as the merged fix simply doesn't work.

the controller keeps responding with 200 instead of 201, but the tests bundled with the "fix" commit do not assert it.

Version-Release number of selected component (if applicable):
# rpm -qa katello
katello-3.9.0-0.1.rc1.el7sat.noarch

satellite6.5.0

Steps to Reproduce:
1. POST a valid payload to host_collections
2. observe the responses return code 


Actual results:
response_code == 200

Expected results:
response_code == 201

Comment 2 Bryan Kearney 2019-11-04 14:34:02 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 9 errata-xmlrpc 2020-10-27 12:57:59 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 (Important: Satellite 6.8 release), 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-2020:4366


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