Closed Bug 1455652 Opened 7 years ago Closed 7 years ago

Async search tasks not registered with Celery

Categories

(developer.mozilla.org Graveyard :: Search, enhancement)

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jwhitlock, Assigned: jwhitlock)

Details

(Keywords: in-triage, Whiteboard: [specification][type:bug])

What did you do? ================ 1. Log into a web container (development w/ "make bash" or production) 2. Run "./manage.py celery inspect registered" What happened? ============== The async search tasks are missing from the registered tasks: kuma.search.tasks.prepare_index kuma.search.tasks.finalize_index What should have happened? ========================== These tasks should be present Is there anything else we should know? ====================================== There may be other tasks that are missing. A possible cause was the refactoring of signals and application configurations in PR 4689 [1]. [1] https://github.com/mozilla/kuma/pull/4689
Assignee: nobody → jwhitlock
Status: NEW → ASSIGNED
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/99480c72a7f9cd4f1887f610aa129195047e10dc bug 1455652: Register async search tasks After the change to AppConfig, search tasks are no longer auto-registering. Force the issue by using CELERY_IMPORTS. Other tasks (wiki, user, etc) are being auto-registered. https://github.com/mozilla/kuma/commit/ffd1df8986b00edcf8c895faff6b71c8c8134f55 Merge pull request #4742 from jwhitlock/search-tasks-1455652 bug 1455652: Register async search tasks
"./manage.py celery inspect registered" shows the registered tasks in production.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.