Re: Upgrading from 1.6.8 to 2.x
elated_model_name]
>> KeyError: u'FileDiffData'
>> Traceback (most recent call last):
>> File "/usr/bin/rb-site", line 9, in
>> load_entry_point('ReviewBoard==2.5.3', 'console_scripts', 'rb-site')()
>> File
>> "/usr/lib/python2.7/site-packages/ReviewBoard-2.5.3-py2.7.egg/reviewboard/cmdline/rbsite.py",
>> line 1922, in main
>> command.run()
>> File
>> "/usr/lib/python2.7/site-packages/ReviewBoard-2.5.3-py2.7.egg/reviewboard/cmdline/rbsite.py",
>> line 1725, in run
>> site.migrate_database()
>> File
>> "/usr/lib/python2.7/site-packages/ReviewBoard-2.5.3-py2.7.egg/reviewboard/cmdline/rbsite.py",
>> line 452, in migrate_database
>> self.run_manage_command("evolve", ["--noinput", "--execute"])
>> File
>> "/usr/lib/python2.7/site-packages/ReviewBoard-2.5.3-py2.7.egg/reviewboard/cmdline/rbsite.py",
>> line 676, in run_manage_command
>> execute_from_command_line([__file__, cmd] + params)
>> File
>> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line
>> 399, in execute_from_command_line
>> utility.execute()
>> File
>> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line
>> 392, in execute
>> self.fetch_command(subcommand).run_from_argv(self.argv)
>> File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
>> line 242, in run_from_argv
>> self.execute(*args, **options.__dict__)
>> File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
>> line 285, in execute
>> output = self.handle(*args, **options)
>> File
>> "/usr/lib/python2.7/site-packages/django_evolution/management/commands/evolve.py",
>> line 65, in handle
>> self.evolve(*app_labels, **options)
>> File
>> "/usr/lib/python2.7/site-packages/django_evolution/management/commands/evolve.py",
>> line 125, in evolve
>> sql.extend(self.evolve_app(app))
>> File
>> "/usr/lib/python2.7/site-packages/django_evolution/management/commands/evolve.py",
>> line 164, in evolve_app
>> app_mutator.run_mutations(mutations)
>> File "/usr/lib/python2.7/site-packages/django_evolution/mutators.py",
>> line 279, in run_mutations
>> self.run_mutation(mutation)
>> File "/usr/lib/python2.7/site-packages/django_evolution/mutators.py",
>> line 268, in run_mutation
>> model_mutator.run_mutation(mutation)
>> File "/usr/lib/python2.7/site-packages/django_evolution/mutators.py",
>> line 165, in run_mutation
>> mutation.mutate(self, self.create_model())
>> File "/usr/lib/python2.7/site-packages/django_evolution/mutations.py",
>> line 446, in mutate
>> self.add_column(mutator, model)
>> File "/usr/lib/python2.7/site-packages/django_evolution/mutations.py",
>> line 450, in add_column
>> self.field_type, self.field_attrs, model)
>> File "/usr/lib/python2.7/site-packages/django_evolution/mutations.py",
>> line 37, in create_field
>> related_model_sig = proj_sig[related_app_name][related_model_name]
>> KeyError: u'FileDiffData'
>>
>>
>>
>>
>> On Wednesday, July 29, 2015 at 7:09:20 PM UTC-6, Christian Hammond wrote:
>>>
>>> Thanks for the follow-up, Risha! I'm glad it's working :) Hopefully this
>>> will help someone else down the road.
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - chri...@beanbaginc.com
>>> Review Board - https://www.reviewboard.org
>>> Beanbag, Inc. - https://www.beanbaginc.com
>>>
>>> On Wed, Jul 29, 2015 at 4:21 PM, Risha Chheda
>>> wrote:
>>>
>>>> I managed to get this to work, just updating this thread.
>>>>
>>>> The problem was that the mysqldump I had done had truncated some of the
>>>> data in the diffviewer_filediff table. I had to gzip the mysqldump
>>>> output and dump it in my test mysql instance. After gzipping the dump was
>>>> 1.6G.
>>>>
>>>> I then converted all the tables from MyISAM to Innodb. Again this was
>>>> failing for the diffviewer_filediff table with the error 'The table is
>>>> full' since the VM I was running this on didn't have enough space. Moving
>>>> to a physical server from the VM fixed this issue. I've attached
Re: Upgrading from 1.6.8 to 2.x
I managed to get this to work, just updating this thread.
The problem was that the mysqldump I had done had truncated some of the
data in the diffviewer_filediff table. I had to gzip the mysqldump output
and dump it in my test mysql instance. After gzipping the dump was 1.6G.
I then converted all the tables from MyISAM to Innodb. Again this was
failing for the diffviewer_filediff table with the error 'The table is
full' since the VM I was running this on didn't have enough space. Moving
to a physical server from the VM fixed this issue. I've attached the
commands I ran along with the mysql settings.
Reviewboard with Docker worked beautifully after that. I just had to run
the docker instance and it installed reviewboard, connected to my database,
performed all the evolutions and started hosting immediately.
Thanks,
Risha
On Tue, Jul 14, 2015 at 12:21 PM, Christian Hammond <
christ...@beanbaginc.com> wrote:
> Hi Risha,
>
> Hmm, I'm not seeing what I was expecting to see there.
>
> It's possible that there's a bug in upgrading to 2.5, due to one of the
> changes we've made. I'm going to be investigating this. For now, I'd
> suggest taking a copy of the 1.6 database and upgrading to the latest 2.0.x
> release instead of 2.5 beta.
>
> Christian
>
> --
> Christian Hammond - christ...@beanbaginc.com
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>
> On Tue, Jul 14, 2015 at 10:14 AM, Risha Chheda
> wrote:
>
>> I'm not sure if it makes any difference but yesterday I ran the rb-site
>> manage evolve --hint and execute commands. I have attached the output of
>> both of those in the attached document. It didn't seem to make a
>> difference, rb-site upgrade still gives me the same issue.
>> rb-site_evolve
>> <https://docs.google.com/document/d/1eg47ZY25Zzx4rOnWk-WWPaUOEF33emWx3S16PruRmZE/edit?usp=drive_web>
>>
>>
>> Here is the output you requested.
>> >>> from django_evolution.models import Version
>> >>> for v in Version.objects.order_by('pk'):
>> ...print '%s - %s - %s' % (v.pk, v.evolutions.count(), v.when)
>> ...
>> 1 - 0 - 2008-05-19 20:11:53+00:00
>> 2 - 0 - 2008-09-24 10:08:29+00:00
>> 3 - 1 - 2008-09-24 10:09:01+00:00
>> 4 - 0 - 2008-10-27 16:17:08+00:00
>> 5 - 1 - 2008-10-27 16:17:25+00:00
>> 6 - 11 - 2011-03-08 05:21:06+00:00
>> 7 - 2 - 2011-10-17 12:15:42+00:00
>> 8 - 0 - 2012-10-13 09:34:28+00:00
>> 9 - 13 - 2012-10-13 09:34:36+00:00
>> 10 - 3 - 2015-07-13 22:41:16+00:00
>>
>>
>> On Tue, Jul 14, 2015 at 2:58 AM, Christian Hammond <
>> christ...@beanbaginc.com> wrote:
>>
>>> Can you run the following:
>>>
>>> $ rb-site manage /path/to/site shell
>>> >>> from django_evolution.models import Version
>>> >>> for v in Version.objects.order_by('pk'):
>>> >>>print '%s - %s - %s' % (v.pk, v.evolutions.count(), v.when)
>>>
>>> That'll give me a sense of what evolutions are applied. There's a
>>> hard-to-diagnose issue that's come up before where an invalid entry ends up
>>> in the history, throwing things off, and this will help me check for that.
>>>
>>> Thanks,
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - christ...@beanbaginc.com
>>> Review Board - https://www.reviewboard.org
>>> Beanbag, Inc. - https://www.beanbaginc.com
>>>
>>> On Mon, Jul 13, 2015 at 3:58 PM, Risha Chheda
>>> wrote:
>>>
>>>> No, that doesn't help either.
>>>>
>>>> # rb-site manage /var/ReviewBoard syncdb
>>>> Creating tables ...
>>>> There are unapplied evolutions for auth.
>>>> The following content types are stale and need to be deleted:
>>>>
>>>> auth | message
>>>>
>>>> Any objects related to these content types by a foreign key will also
>>>> be deleted. Are you sure you want to delete these content types?
>>>> If you're unsure, answer 'no'.
>>>>
>>>> Type 'yes' to continue, or 'no' to cancel: yes
>>>> There are unapplied evolutions for contenttypes.
>>>> There are unapplied evolutions for accounts.
>>>> There are unapplied evolutions for attachments.
>>>> There are unapplied evolutions for changedescs.
>>>> There are unapplied evolutions for diffviewer.
>>>> There are unapp
Re: Upgrading from 1.6.8 to 2.x
I'm not sure if it makes any difference but yesterday I ran the rb-site
manage evolve --hint and execute commands. I have attached the output of
both of those in the attached document. It didn't seem to make a
difference, rb-site upgrade still gives me the same issue.
rb-site_evolve
<https://docs.google.com/document/d/1eg47ZY25Zzx4rOnWk-WWPaUOEF33emWx3S16PruRmZE/edit?usp=drive_web>
Here is the output you requested.
>>> from django_evolution.models import Version
>>> for v in Version.objects.order_by('pk'):
...print '%s - %s - %s' % (v.pk, v.evolutions.count(), v.when)
...
1 - 0 - 2008-05-19 20:11:53+00:00
2 - 0 - 2008-09-24 10:08:29+00:00
3 - 1 - 2008-09-24 10:09:01+00:00
4 - 0 - 2008-10-27 16:17:08+00:00
5 - 1 - 2008-10-27 16:17:25+00:00
6 - 11 - 2011-03-08 05:21:06+00:00
7 - 2 - 2011-10-17 12:15:42+00:00
8 - 0 - 2012-10-13 09:34:28+00:00
9 - 13 - 2012-10-13 09:34:36+00:00
10 - 3 - 2015-07-13 22:41:16+00:00
On Tue, Jul 14, 2015 at 2:58 AM, Christian Hammond wrote:
> Can you run the following:
>
> $ rb-site manage /path/to/site shell
> >>> from django_evolution.models import Version
> >>> for v in Version.objects.order_by('pk'):
> >>>print '%s - %s - %s' % (v.pk, v.evolutions.count(), v.when)
>
> That'll give me a sense of what evolutions are applied. There's a
> hard-to-diagnose issue that's come up before where an invalid entry ends up
> in the history, throwing things off, and this will help me check for that.
>
> Thanks,
>
> Christian
>
> --
> Christian Hammond - christ...@beanbaginc.com
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>
> On Mon, Jul 13, 2015 at 3:58 PM, Risha Chheda
> wrote:
>
>> No, that doesn't help either.
>>
>> # rb-site manage /var/ReviewBoard syncdb
>> Creating tables ...
>> There are unapplied evolutions for auth.
>> The following content types are stale and need to be deleted:
>>
>> auth | message
>>
>> Any objects related to these content types by a foreign key will also
>> be deleted. Are you sure you want to delete these content types?
>> If you're unsure, answer 'no'.
>>
>> Type 'yes' to continue, or 'no' to cancel: yes
>> There are unapplied evolutions for contenttypes.
>> There are unapplied evolutions for accounts.
>> There are unapplied evolutions for attachments.
>> There are unapplied evolutions for changedescs.
>> There are unapplied evolutions for diffviewer.
>> There are unapplied evolutions for hostingsvcs.
>> There are unapplied evolutions for reviews.
>> There are unapplied evolutions for scmtools.
>> There are unapplied evolutions for site.
>> Project signature has changed - an evolution is required
>> Installing custom SQL ...
>> Installing indexes ...
>> Installed 0 object(s) from 0 fixture(s)
>>
>>
>> root@05e83c8f5ab7:/# rb-site upgrade /var/ReviewBoard
>> ..
>> ..
>>
>>
>>
>> On Mon, Jul 13, 2015 at 3:26 PM, Christian Hammond <
>> christ...@beanbaginc.com> wrote:
>>
>>> Hi Risha,
>>>
>>> That's strange. It's like some state is missing there.
>>>
>>> Can you try doing this first:
>>>
>>> $ rb-site manage /var/ReviewBoard syncdb
>>>
>>> and then do the upgrade? See if that gets any further.
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - christ...@beanbaginc.com
>>> Review Board - https://www.reviewboard.org
>>> Beanbag, Inc. - https://www.beanbaginc.com
>>>
>>> -Original Message-
>>> From: Risha Chheda
>>> Reply: reviewboard@googlegroups.com >
>>> Date: July 13, 2015 at 3:24:20 PM
>>> To: reviewboard@googlegroups.com >
>>> Subject: Upgrading from 1.6.8 to 2.x
>>>
>>> > Hi,
>>> >
>>> > I am trying to upgrade reviewboard from 1.6.8 to 2.5.beta and
>>> everytime I
>>> > get this traceback:
>>> > mysql version I'm testing against is 5.6.25.
>>> >
>>> > Both reviewboard and mysql are running in their own docker containers
>>> on
>>> > the same VM.
>>> > I tried upgrading from 1.6.8 to 2.0.18 as well, but I get the same
>>> issue.
>>> >
>>> > # rb-site upgrade /var/ReviewBoard
>>> > Rebuilding directory structure
>>> > Updating database. This may take a while.
>>> >
>>> > The
Re: Upgrading from 1.6.8 to 2.x
No, that doesn't help either. # rb-site manage /var/ReviewBoard syncdb Creating tables ... There are unapplied evolutions for auth. The following content types are stale and need to be deleted: auth | message Any objects related to these content types by a foreign key will also be deleted. Are you sure you want to delete these content types? If you're unsure, answer 'no'. Type 'yes' to continue, or 'no' to cancel: yes There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. There are unapplied evolutions for site. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) root@05e83c8f5ab7:/# rb-site upgrade /var/ReviewBoard .. .. On Mon, Jul 13, 2015 at 3:26 PM, Christian Hammond wrote: > Hi Risha, > > That's strange. It's like some state is missing there. > > Can you try doing this first: > > $ rb-site manage /var/ReviewBoard syncdb > > and then do the upgrade? See if that gets any further. > > Christian > > -- > Christian Hammond - christ...@beanbaginc.com > Review Board - https://www.reviewboard.org > Beanbag, Inc. - https://www.beanbaginc.com > > -Original Message- > From: Risha Chheda > Reply: reviewboard@googlegroups.com > > Date: July 13, 2015 at 3:24:20 PM > To: reviewboard@googlegroups.com > > Subject: Upgrading from 1.6.8 to 2.x > > > Hi, > > > > I am trying to upgrade reviewboard from 1.6.8 to 2.5.beta and everytime I > > get this traceback: > > mysql version I'm testing against is 5.6.25. > > > > Both reviewboard and mysql are running in their own docker containers on > > the same VM. > > I tried upgrading from 1.6.8 to 2.0.18 as well, but I get the same issue. > > > > # rb-site upgrade /var/ReviewBoard > > Rebuilding directory structure > > Updating database. This may take a while. > > > > The log output below, including warnings and errors, > > can be ignored unless upgrade fails. > > > > -- -- > > Creating tables ... > > There are unapplied evolutions for auth. > > There are unapplied evolutions for contenttypes. > > There are unapplied evolutions for accounts. > > There are unapplied evolutions for attachments. > > There are unapplied evolutions for changedescs. > > There are unapplied evolutions for diffviewer. > > There are unapplied evolutions for hostingsvcs. > > There are unapplied evolutions for reviews. > > There are unapplied evolutions for scmtools. > > There are unapplied evolutions for site. > > Project signature has changed - an evolution is required > > Installing custom SQL ... > > Installing indexes ... > > Installed 0 object(s) from 0 fixture(s) > > ERROR:root:Unexpected error: u'FileDiffData' > > Traceback (most recent call last): > > File > > > "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/management/commands/evolve.py", > > line 65, in handle > > self.evolve(*app_labels, **options) > > File > > > "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/management/commands/evolve.py", > > line 125, in evolve > > sql.extend(self.evolve_app(app)) > > File > > > "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/management/commands/evolve.py", > > line 164, in evolve_app > > app_mutator.run_mutations(mutations) > > File > > > "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutators.py", > > line 279, in run_mutations > > self.run_mutation(mutation) > > File > > > "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutators.py", > > line 268, in run_mutation > > model_mutator.run_mutation(mutation) > > File > > > "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutators.py", > > line 165, in run_mutation > > mutation.mutate(self, self.create_model()) > > File > > > "/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutations.py", > >
Upgrading from 1.6.8 to 2.x
Hi,
I am trying to upgrade reviewboard from 1.6.8 to 2.5.beta and everytime I
get this traceback:
mysql version I'm testing against is 5.6.25.
Both reviewboard and mysql are running in their own docker containers on
the same VM.
I tried upgrading from 1.6.8 to 2.0.18 as well, but I get the same issue.
# rb-site upgrade /var/ReviewBoard
Rebuilding directory structure
Updating database. This may take a while.
The log output below, including warnings and errors,
can be ignored unless upgrade fails.
-- --
Creating tables ...
There are unapplied evolutions for auth.
There are unapplied evolutions for contenttypes.
There are unapplied evolutions for accounts.
There are unapplied evolutions for attachments.
There are unapplied evolutions for changedescs.
There are unapplied evolutions for diffviewer.
There are unapplied evolutions for hostingsvcs.
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
There are unapplied evolutions for site.
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
Installed 0 object(s) from 0 fixture(s)
ERROR:root:Unexpected error: u'FileDiffData'
Traceback (most recent call last):
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/management/commands/evolve.py",
line 65, in handle
self.evolve(*app_labels, **options)
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/management/commands/evolve.py",
line 125, in evolve
sql.extend(self.evolve_app(app))
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/management/commands/evolve.py",
line 164, in evolve_app
app_mutator.run_mutations(mutations)
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutators.py",
line 279, in run_mutations
self.run_mutation(mutation)
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutators.py",
line 268, in run_mutation
model_mutator.run_mutation(mutation)
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutators.py",
line 165, in run_mutation
mutation.mutate(self, self.create_model())
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutations.py",
line 446, in mutate
self.add_column(mutator, model)
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutations.py",
line 450, in add_column
self.field_type, self.field_attrs, model)
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/mutations.py",
line 37, in create_field
related_model_sig = proj_sig[related_app_name][related_model_name]
KeyError: u'FileDiffData'
Traceback (most recent call last):
File "/usr/local/bin/rb-site", line 9, in
load_entry_point('ReviewBoard==2.5beta1', 'console_scripts',
'rb-site')()
File
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5beta1-py2.7.egg/reviewboard/cmdline/rbsite.py",
line 1885, in main
command.run()
File
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5beta1-py2.7.egg/reviewboard/cmdline/rbsite.py",
line 1694, in run
site.migrate_database()
File
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5beta1-py2.7.egg/reviewboard/cmdline/rbsite.py",
line 438, in migrate_database
self.run_manage_command("evolve", ["--noinput", "--execute"])
File
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.5beta1-py2.7.egg/reviewboard/cmdline/rbsite.py",
line 662, in run_manage_command
execute_from_command_line([__file__, cmd] + params)
File
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/core/management/__init__.py",
line 399, in execute_from_command_line
utility.execute()
File
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/core/management/__init__.py",
line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/core/management/base.py",
line 242, in run_from_argv
self.execute(*args, **options.__dict__)
File
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/core/management/base.py",
line 285, in execute
output = self.handle(*args, **options)
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/management/commands/evolve.py",
line 65, in handle
self.evolve(*app_labels, **options)
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0.7.5-py2.7.egg/django_evolution/management/commands/evolve.py",
line 125, in evolve
sql.extend(self.evolve_app(app))
File
"/usr/local/lib/python2.7/dist-packages/django_evolution-0
