Bug 1461188
Summary: | Creating an ActivationKey with "contentOverrides": null results in a 400 status | ||
---|---|---|---|
Product: | [Community] Candlepin | Reporter: | Shayne Riley <sriley> |
Component: | candlepin | Assignee: | candlepin-bugs |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Katello QA List <katello-qa-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 2.0 | CC: | khowell, ojanus, redakkan, skallesh, sriley |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | candlepin-2.7.1-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-24 17:37:43 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
Shayne Riley
2017-06-13 18:58:15 UTC
Specifying... "releaseVer": null ... Also generates the same 400 status, but for a different field. The fix (check for null) is nearly the same, but for a different method. In ActivationKey#setReleaseVer, line 329: public void setReleaseVer(Release releaseVer) { if (releaseVer != null) { this.releaseVer = releaseVer.getReleaseVer(); } else { this.releaseVer = null; } } Is this a difference in behavior between CP 2.0 and previous versions? If we don't make any changes, is this going to break anything? In Candlepin 0.9.51.24 if you attempt to create an activation key and specify... "contentOverrides": null ...within the JSON, a 500 status is generated instead of the 400 status. So it seems that this bug existed since before Candlepin 2.0. I'd argue that, despite this, it should be fixed anyway. |