-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
Unset
-
None
-
Platform Pipeline Sprint 39, Platform Pipeline Sprint 40, Platform Pipeline Sprint 41
-
Moderate
This week we integrated Payload Tracker with Turnpike in stage and this change seems to caused an issue in the communication between Ingress and Payload tracker.
All the calls to the Ingress /track endpoint are now returning 403s.
How to reproduce:
curl -k --user *******:****** --proxy ******* "https://cloud.stage.redhat.com/api/ingress/v1/track/528c6da8a0e74defa274bcbec21aabe9" -v
Expected result:
200 response
Actual result:
403 (forbidden) response
- relates to
-
RHCLOUD-21707 Periodic HTTP 403s from payload tracker
-
- Closed
-