René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"registry-rest-api-tests CI workflow sometimes fails due to missing HTTP readiness check","articleBody":"## Problem                                                                                                                                                                                                 \nThe registry-rest-api-tests workflow (pr-rest-API-tests) is structurally flaky. When it fails, all 28 tests fail with the same error: \n`assert 502 == 200`\nThis happens across multiple branches (master, fix_complex_type, dependabot/*, etc.) and is not caused by any specific code change.\n\n## Suspected Root Cause \nThe test fixture checks two conditions before starting tests:\n  1. Pod status → Running\n  2. FeatureStore CR status → Ready\n\nHowever, 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.\n\n## Possible Solution \nadd 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:\n\n\n","author":{"url":"https://github.com/soooojinlee","@type":"Person","name":"soooojinlee"},"datePublished":"2026-02-17T07:28:15.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/5977/feast/issues/5977"}