fix: Ignore supervisor "already started" when ensuring edxapp workers…#358
Merged
srathod-apphelix merged 2 commits intoJul 21, 2026
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Adjusts the edxapp deploy flow to tolerate Supervisor’s ERROR (already started) when ensuring edxapp_worker processes are started, preventing sandbox provisioning failures when Datadog instrumentation causes workers to be started earlier in the run.
Changes:
- Registers the
supervisorctl“ensure edxapp_workers has started” task result. - Adds a
failed_whenguard to treat “already started” as non-fatal for that task.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ktyagiapphelix2u
approved these changes
Jul 21, 2026
srathod-apphelix
force-pushed
the
srathod/GSRE-4236-edxapp-ignore-workers-already-started
branch
from
July 21, 2026 06:35
6733eac to
2cc5d94
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (1)
playbooks/roles/edxapp/tasks/deploy.yml:509
failed_whenreferencesedxapp_workers_start.faileddirectly. In Ansible, registered results may not have afailedattribute on success, and accessing a missing attribute inside a conditional can raise an error (elsewhere in this repo, similar logic is guarded with...failed is defined, e.g.playbooks/roles/mongo_7_0/tasks/main.yml:102). Guard the access so successful runs don’t error while evaluating this expression.
failed_when: >
edxapp_workers_start is failed and
'already started' not in edxapp_workers_start.msg
srathod-apphelix
deleted the
srathod/GSRE-4236-edxapp-ignore-workers-already-started
branch
July 21, 2026 06:37
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
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
ERROR (already started)as success when ensuringedxapp_workerprocesses are started.deploy.ymlrole copies.Jira - GSRE-4236
Purpose
CreateSandbox fails only when
enable_datadog=truebecause Datadog changes worker startup scripts (ddtrace-run), sosupervisorctl updatestarts the workers, and the laterensure edxapp_workers has startedtask fails with:edxapp_worker:cms_default_1: ERROR (already started)This change makes that condition non-fatal so sandbox provisioning can continue, while the final
restart edxapp_workerstask still reloads the newly deployed code.Changes
playbooks/roles/edxapp/tasks/deploy.yml