Conversation
Worker heartbeat registration in online_workers lags behind pod readiness after minor upgrades, causing OperatorFinishedExecution to never post. Worker availability is already covered by the Automationhub-Worker-Ready condition from pod readiness probes. Issue: AAP-88907 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Funi1234
changed the title
Funi1234
requested review from
dsavineau,
jamesmarshall24,
lucas-benedito and
rooftopcellist
August 20, 2026 15:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SUMMARY
Remove the
online_workerscheck from theuriuntilcondition in the galaxy-status version check (both route and non-route paths).After a minor upgrade, worker pods restart quickly and
Automationhub-Worker-Readyis set toTruevia pod readiness probes, but workers take significantly longer to re-register their heartbeat with Redis/Celery and appear inonline_workers. This causes theuritask to exhaust its retry window, preventingOperatorFinishedExecutionfrom ever being posted — even though the Hub deployment is functionally healthy.The remaining health gates (API responding, plugin versions registered, content apps up, database connected, Redis connected) are sufficient. Worker availability is already covered by the
Automationhub-Worker-Readycondition.Issue: AAP-88907
ADDITIONAL INFORMATION
The failure surfaces as a misleading
Failurecondition message of"OK (2014 bytes)"on the AutomationHub CR — the HTTP 200 response was successful, but the Jinja2untilassertion ononline_workersfailed after retry exhaustion, andansible-operator-pluginscaptured the lastmsgas the condition message.