(FSE Dry run 1) Requests using Edge URL return 503 error

Description

Preconditions:

  • Edge user exists in the system and has Edge API key

Steps to Reproduce:

  1. Perform the following API call:

    1. GET <<edge URL>>/rtac/<< existing instance UUID>>?apikey=edgeAPIKey

Actual Results: Response with 503 status is returned with following body:

Expected Results: Response with 200 status is returned with body containing information about the instance. Example of the body:

Additional Information:

  • NOT reproducible on evrk2, Snapshot

  • The same response for other requests using Edge URL and API key, for example:

    • {{edgeUrl}}/courses/reserves

    • {{edgeUrl}}/patron/account/externalsystemid:<<external system ID of existing user>>

  • See example:

Environment

None

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Estimation Notes and Assumptions

None

RCA Group Details

None

Attachments

3

Checklist

hide

Activity

Show:

Yauhen Viazau July 26, 2024 at 9:47 AM

Re-tested on FSE Dry run 1 - works as expected

API calls which use Edge URL are executed as expected, including a call to /rtac. See examples (the last two calls are expected to yield 403 response):

 

Michelle Suranofsky July 26, 2024 at 1:57 AM

- I tested on dryrun 1 and I get a good response back. (/rtac/instanceid?apikey=apikey) thank you!

Yauhen Viazau July 23, 2024 at 12:39 PM

- please review/fix the issue from the previous comment

Yauhen Viazau July 19, 2024 at 1:11 PM
Edited

Tested on FSE Dry run 1

A call to /rtac is still failing with 502 error.
Other two are working as expected.
See example:

 

Done

Details

Assignee

Reporter

Development Team

Eureka

RCA Group

TBD

Story Points

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created July 19, 2024 at 10:33 AM
Updated July 26, 2024 at 9:47 AM
Resolved July 26, 2024 at 9:47 AM
TestRail: Cases
TestRail: Runs