migrations do not work on new install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charmworld |
Fix Released
|
Critical
|
Curtis Hovey |
Bug Description
The redeploy of staging.
HOOK + '[' true == true ']'
HOOK + cd /home/webops_
HOOK + su charmworld -c 'INI=/home/
HOOK Traceback (most recent call last):
HOOK File "bin/migrations", line 9, in <module>
HOOK load_entry_
HOOK File "/home/
HOOK args.func(ini, args)
HOOK File "/home/
HOOK new_version = migrations.
HOOK File "/home/
HOOK self.run_
HOOK File "/home/
HOOK getattr(module, 'upgrade')(db, index_client)
HOOK File "/home/
HOOK index_client.
HOOK File "/home/
HOOK return func(*args, query_params=
HOOK File "/home/
HOOK query_params=
HOOK File "/home/
HOOK self._raise_
HOOK File "/home/
HOOK raise error_class(
HOOK pyelasticsearch
Related branches
- Benji York (community): Approve
-
Diff: 79 lines (+25/-11)2 files modifiedcharmworld/migrations/versions/018_delete_all_bundles.py (+11/-3)
charmworld/migrations/versions/tests/test_migrations.py (+14/-8)
Changed in charmworld: | |
assignee: | nobody → Curtis Hovey (sinzui) |
status: | Triaged → In Progress |
Changed in charmworld: | |
status: | In Progress → Fix Released |
I hacked the the migration script to complete so that staging could start ingestion.
While mongodb is forgiving when collections do not exist, elasticsearch is not. ES updates may need guard to ensure there is something to migrate.