Payload tracker periodically returns HTTP 403s to requests. It's unclear to me why this is happening:

• The client is using valid credentials when making requests to CRC.
• The client is authenticating using the same account to which the insights-client archive was uploaded.
• In every case I've observed, the client makes a series of successful, otherwise-identical requests before the 403-producing request.

This is causing a significant rate of failure in the night-time runs of the end-to-end tests. For more on this, see REMEDY-231, especially REMEDY-231 (comment).

I'm filing this bug against payload tracker because the 403s are returned in response to requests to URLs like https://cloud.redhat.com/api/ingress/v1/track/6e989dc2bddc4e6f85ecc0ad5f4c7d20.