Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Create package with existed name throw 500 error

Description

If package with given name already exist, POST package endpoint will respond with Internal Server Error

Expected result: the response status is 400

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Shans Kaluhin March 10, 2023 at 11:35 AM


All knowledge base credentials returns right response now.
Bug can be closed.

Pavlo Smahin September 28, 2022 at 4:54 PM

, is the bug still reproducible?
cc:

Shans Kaluhin September 5, 2022 at 11:51 AM
Edited

But works for apidvcorp customer id

Shans Kaluhin September 5, 2022 at 11:36 AM
Edited

apie2esch1, apidvgvmt and apidvgvmt SandBox still returns 500 error code

 

 

Pavlo Smahin June 15, 2022 at 9:10 AM
Edited

, the response status code is changed from HoldingsIQ API. We are expecting to have 400 status but got 500 for this type of error when we try to create a package with an already existing name. Should we change handling the error from our side or there is some problems with API?

Cannot Reproduce

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

Release

Not Scheduled

RCA Group

Third party component integration

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created June 10, 2022 at 12:58 PM
Updated March 10, 2023 at 2:17 PM
Resolved March 10, 2023 at 2:17 PM
Configure
TestRail: Cases
TestRail: Runs