Description

soooojinlee

opened on Feb 17, 2026

Issue body actions

Problem

The registry-rest-api-tests workflow (pr-rest-API-tests) is structurally flaky. When it fails, all 28 tests fail with the same error:
assert 502 == 200
This happens across multiple branches (master, fix_complex_type, dependabot/*, etc.) and is not caused by any specific code change.

Suspected Root Cause

The test fixture checks two conditions before starting tests:

1. Pod status → Running
2. FeatureStore CR status → Ready

However, the HTTP endpoint behind the ingress may not be ready to serve traffic even when Pod/CR are Ready. Tests start immediately, hitting the ingress before the backend is fully initialized, resulting in 502 Bad Gateway responses.

Possible Solution

add an HTTP readiness poll to the test fixture in sdk/python/tests/integration/registration/rest_api/test_registry_rest_api.py. After confirming Pod/CR readiness, poll the actual HTTP endpoint until it returns 200 before starting tests:

Activity

1. soooojinlee

   added

   kind/bug

   priority/p2

   on Feb 17, 2026
2. mstfzhoseini-sketch commented on Feb 17, 2026

   

   mstfzhoseini-sketch

   on Feb 17, 2026

   More actions

   Hello,

   I’ve gone through this issue and I’m confident I can address the CI instability in the registry-rest-api-tests workflow.

   My background includes backend development and CI reliability work, particularly around HTTP service readiness, integration test timing, and race-condition failures. I can investigate the root cause and submit a focused PR to make the workflow deterministic.

   Let me know if you’d like me to take this on.

   Best regards,
3. soooojinlee commented on Feb 17, 2026

   

   soooojinlee

   on Feb 17, 2026

   ContributorAuthor

   More actions

   Hi @mstfzhoseini-sketch, thanks for the interest! Just a heads up — there's already a PR addressing this issue: #5978.
4. ntkathole

   closed this as completedin #5978on Feb 23, 2026
5. ntkathole commented on Feb 23, 2026

   

   ntkathole

   on Feb 23, 2026

   Member

   More actions

   Even after adding checks and timeout 180s, I see sometimes registry server won't get ready

   Waiting for HTTP endpoint to become ready (timeout=180s): http://feast.kind.test/api/v1/projects
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   HTTP endpoint returned 502, retrying in 5s...
   
   Deleting namespace: test-ns-feast-rest
   ERROR
   

   https://github.com/feast-dev/feast/actions/workflows/registry-rest-api-tests.yml?query=is%3Afailure

   @mstfzhoseini-sketch See if you can resolve this
6. ntkathole

   reopened this on Feb 23, 2026
7. ntkathole

   closed this as completedin #6111on Mar 16, 2026

Issue actions