Error while upgrading rb-site

38 views
Skip to first unread message

Sai Krishna Reddy

unread,
Jul 29, 2025, 8:34:31 AMJul 29
to Review Board Community
Hi, while trying to upgrade reviewboard using rb-site upgrade encountering the following error, I'm currently using latest version of django-evolution. 

2025-07-29T11:55:15.508300Z app[web.1]: [33;40m Upgrading the Review Board site directory [0m
2025-07-29T11:55:15.508333Z app[web.1]:
2025-07-29T11:55:15.508223Z app[web.1]: [33;40m———————————————————————————————————————————————————————————————————————————————— [0m
2025-07-29T11:55:15.508320Z app[web.1]: [33;40m———————————————————————————————————————————————————————————————————————————————— [0m
2025-07-29T11:55:15.515928Z app[web.1]: Rebuilding directory structure ... OK
2025-07-29T11:55:16.555698Z app[web.1]: Traceback (most recent call last):
2025-07-29T11:55:16.555893Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/reviewboard/cmdline/rbsite.py", line 3320, in main
2025-07-29T11:55:16.555770Z app[web.1]:   File "/app/.heroku/python/bin/rb-site", line 8, in <module>
2025-07-29T11:55:16.556221Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/reviewboard/cmdline/rbsite.py", line 2837, in run
2025-07-29T11:55:16.556192Z app[web.1]:     command.run(site, options)
2025-07-29T11:55:16.555858Z app[web.1]:     sys.exit(main())
2025-07-29T11:55:16.556675Z app[web.1]:     diff = evolver.diff_evolutions()
2025-07-29T11:55:16.556640Z app[web.1]:     site.update_database(report_progress=True)
2025-07-29T11:55:16.556712Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/evolve/evolver.py", line 261, in diff_evolutions
2025-07-29T11:55:16.556824Z app[web.1]:     self._prepare_tasks()
2025-07-29T11:55:16.556878Z app[web.1]:     task_cls.prepare_tasks(evolver=self,
2025-07-29T11:55:16.556854Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/evolve/evolver.py", line 459, in _prepare_tasks
2025-07-29T11:55:16.556958Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/evolve/evolve_app_task.py", line 118, in prepare_tasks
2025-07-29T11:55:16.556665Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/reviewboard/cmdline/rbsite.py", line 604, in update_database
2025-07-29T11:55:16.557048Z app[web.1]:     task.prepare(**kwargs)
2025-07-29T11:55:16.556994Z app[web.1]:     super(EvolveAppTask, cls).prepare_tasks(
2025-07-29T11:55:16.557234Z app[web.1]:     mutations_info = self.generate_mutations_info(
2025-07-29T11:55:16.557027Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/evolve/base.py", line 68, in prepare_tasks
2025-07-29T11:55:16.557101Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/evolve/evolve_app_task.py", line 1312, in prepare
2025-07-29T11:55:16.557341Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/evolve/evolve_app_task.py", line 1178, in generate_mutations_info
2025-07-29T11:55:16.557463Z app[web.1]:     app_mutator.run_mutations(mutations)
2025-07-29T11:55:16.557521Z app[web.1]:     self.run_mutation(mutation)
2025-07-29T11:55:16.557506Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/mutators/app_mutator.py", line 173, in run_mutations
2025-07-29T11:55:16.557537Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/mutators/app_mutator.py", line 166, in run_mutation
2025-07-29T11:55:16.557555Z app[web.1]:     mutator.run_mutation(mutation)
2025-07-29T11:55:16.557564Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/mutators/model_mutator.py", line 320, in run_mutation
2025-07-29T11:55:16.557764Z app[web.1]:     mutation.mutate(self, **mutate_kwargs)
2025-07-29T11:55:16.557633Z app[web.1]:     super(ModelMutator, self).run_mutation(
2025-07-29T11:55:16.557788Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/mutations/add_field.py", line 131, in mutate
2025-07-29T11:55:16.557667Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/mutators/base.py", line 154, in run_mutation
2025-07-29T11:55:16.558712Z app[web.1]:     self.add_column(mutator, model)
2025-07-29T11:55:16.558770Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/mutations/add_field.py", line 143, in add_column
2025-07-29T11:55:16.558790Z app[web.1]:     field = self._create_field(mutator, model)
2025-07-29T11:55:16.558808Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/mutations/add_field.py", line 206, in _create_field
2025-07-29T11:55:16.558838Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/mock_models.py", line 61, in create_field
2025-07-29T11:55:16.558825Z app[web.1]:     return create_field(project_sig=mutator.project_sig,
2025-07-29T11:55:16.558851Z app[web.1]:     project_sig
2025-07-29T11:55:16.558861Z app[web.1]:   File "/app/.heroku/python/lib/python3.9/site-packages/django_evolution/signature.py", line 839, in get_model_sig
2025-07-29T11:55:16.558884Z app[web.1]: django_evolution.errors.MissingSignatureError: Unable to find a model signature for "oauth2_provider.IDToken". syncdb/migrate might need to be run first.

Can anyone help to suggest how to fix it? Thanks in advance.

 

Christian Hammond

unread,
Jul 30, 2025, 12:16:44 AMJul 30
to revie...@googlegroups.com
Hi,

Can you tell me what version you're upgrading from and to?

Also, what kind of database is this?

Christian

--
Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups "Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/reviewboard/b868c33b-7128-465a-99d5-faadddf75d5dn%40googlegroups.com.


--
Christian Hammond
President/CEO of Beanbag
Makers of Review Board

Sai Krishna Reddy

unread,
Jul 30, 2025, 9:49:04 AMJul 30
to Review Board Community
Thanks for the response Christian, I'm upgrading from 3.0.20 to 5.0.7. And I'm using postgres database.

Christian Hammond

unread,
Jul 31, 2025, 8:05:39 PMJul 31
to revie...@googlegroups.com
Hi Sai,

Review Board 5 is no longer supported outside of a support contract. If you need to be on that version, I can reach out about what we offer under a contract and how we can help get this sorted (it’ll involve custom backports to that release).

There have been many fixes and improvements to the upgrade process since Review Board 5, and that specific issue (upgrading from a 3-era database) has specifically seen fixes.

My recommendation would be to upgrade to Review Board 7 instead. That’ll have the best chance of working, access to bug and security fixes, and many improvements over 5.

Christian

--
Christian Hammond
President/CEO of Beanbag
Makers of Review Board

Reply all
Reply to author
Forward
0 new messages