Hi Eric,

Glad it works!

One suggestion I'd have is to let easy_install do its job with dependencies, 
rather than trying to manage them all in Ansible. Otherwise you're going to 
spend a lot of time trying to match up the dependencies. We've seen some users 
do this and end up with things crashing because they missed one.

Christian

--  
Christian Hammond - christ...@beanbaginc.com  
Review Board - https://www.reviewboard.org  
Beanbag, Inc. - https://www.beanbaginc.com

-----Original Message-----
From: Eric Johnson <e...@tibco.com>
Reply: reviewboard@googlegroups.com <reviewboard@googlegroups.com>>
Date: February 12, 2015 at 9:25:04 AM
To: David Trowbridge <trowb...@gmail.com>>
Cc: reviewboard@googlegroups.com <reviewboard@googlegroups.com>>
Subject:  Re: Crazy difficulties trying to upgrade from 1.7.7.1 - any tool for 
finding/correcting DB problems?

> Hi David, Christian,
>  
> Thanks for your help so far!
>  
> Yesterday, I was able to find the time between meetings to try the
> conversion approach that Christian suggested, and it appeared to work. I
> have to test it again today, to make sure I didn't somehow trick myself.
>  
> As for jumping to the later release, I plan to jump to 1.7.28. In typical
> debugging fashion, I was trying to reduce the problem to the minimum
> possible scope, and identify exactly where the problem occurred, and
> eliminate any possible confounding issues. So I first tried a 1.7.28
> upgrade, but when that failed, jumped to testing the upgrade to 1.7.8.
>  
> In my local environment, a few days back, I completed scripting the
> installation/configuration of ReviewBoard using Ansible. So I can spin up a
> test environment that mirrors my production environment. And, an upgrade is
> theoretically just changing the version of ReviewBoard installed (and a few
> other tidbits, like Django & its ilk) in my Ansible script, and running the
> update. As soon as I can find the time do that, I will!
>  
> Using that script to attempt the upgrade in the first place is what led me
> to the current issues. I'm not jumping straight to 2.0.X yet, because I
> want to understand how best to configure for our environment. Thanks for
> checking!
>  
> Eric.
>  
>  
> On Wed, Feb 11, 2015 at 1:21 PM, David Trowbridge  
> wrote:
>  
> > One more question-- is there a reason why you're going 1.7.7.1 -> 1.7.8,
> > instead of just jumping straight to the latest 1.7.x (or even latest
> > 2.0.x)? There have been a great many bugs fixed since 1.7.8, including, I
> > believe, some about key lengths with mysql utf-8 indexes.
> >
> > -David
> >
> > On Wed Feb 11 2015 at 12:30:59 PM Christian Hammond <
> > christ...@beanbaginc.com> wrote:
> >
> >> Hi Eric,
> >>
> >> It sounds like a lot of the problems boil down to the MyISAM vs. InnoDB
> >> incompatibility. I recommend altering the tables using the MySQL command
> >> line and not a dump/load. You should be able to do this by performing the
> >> following on each table:
> >>
> >> ALTER TABLE `tablename` ENGINE=InnoDB;
> >>
> >> You'd need to do this for *all* tables. From an answer on this
> >> StackOverflow (http://stackoverflow.com/questions/3856435/how-to-
> >> convert-all-tables-from-myisam-into-innodb), you can do:
> >>
> >> SET @DATABASE_NAME = 'name_of_your_db';
> >>
> >> SELECT CONCAT('ALTER TABLE `', table_name, '` ENGINE=InnoDB;') AS
> >> sql_statements
> >> FROM information_schema.tables AS tb
> >> WHERE table_schema = @DATABASE_NAME
> >> AND `ENGINE` = 'MyISAM'
> >> AND `TABLE_TYPE` = 'BASE TABLE'
> >> ORDER BY table_name DESC;
> >>
> >>
> >> I'd test all this on a backup first.
> >>
> >> Once you do that, I would expect a simple rb-site upgrade to work. You
> >> shouldn't need to do any database dumps/loads for any of this.
> >>
> >> Do you have a list of the schema changes you've made to your database? It
> >> sounded like there was at least one. If there are more, you may run into
> >> issues down the road as you upgrade.
> >>
> >> Completely optional, but we offer direct assistance with difficult
> >> upgrades due to things like schema changes or other problems as part of a
> >> support contract, where we'll grab a copy of the database schema and figure
> >> out exactly what it'd take to get a successful upgrade going. I'm also
> >> happy to help on here, of course, but if this ends up becoming very hard to
> >> diagnose, that could be a suitable option for you.
> >>
> >> Christian
> >>
> >> --
> >> Christian Hammond - christ...@beanbaginc.com
> >> Review Board - https://www.reviewboard.org
> >> Beanbag, Inc. - https://www.beanbaginc.com
> >>
> >> -----Original Message-----
> >> From: e...@tibco.com  
> >> Reply: reviewboard@googlegroups.com >
> >> Date: February 11, 2015 at 11:15:06 AM
> >> To: reviewboard@googlegroups.com >
> >> Subject: Crazy difficulties trying to upgrade from 1.7.7.1 - any tool
> >> for finding/correcting DB problems?
> >>
> >> > My company has been using ReviewBoard successfully for quite some time,
> >> and
> >> > everyone seems to like it.
> >> >
> >> > However, I'm trying to upgrade past 1.7.7.1, and run into a bevy of
> >> trouble.
> >> >
> >> > Just running the site upgrade didn't work - perhaps something weird
> >> about
> >> > my configuration, but on the target machines, if I have my 1.7.7.1 MySQL
> >> > MyISAM tables, they refuse to upgrade even to 1.7.8. (I did this with an
> >> > *empty* database with no reviews in it, and it still didn't migrate). If
> >> > the starting database is uses the InnoDB engine, the upgrade to 1.7.8
> >> > fails, because a key gets too big). Apparently, I can work around *that*
> >> > problem by sticking:
> >> >
> >> > innodb_large_prefix=on
> >> >
> >> > into /etc/mysql/my.cnf
> >> >
> >> > OK, so the strategy to move forward seem to be to migrate all my data
> >> from
> >> > MyISAM to InnoDB via rb-site manage .... dumbdb and loaddb. However,
> >> that
> >> > *also* "fails" in the sense that not all my data is being imported, due
> >> to
> >> > foreign key problems. I started looking at them, and realized that some
> >> of
> >> > them are genuine problems that must some how be addressed.
> >> >
> >> > - last_login being null (my fault, due to integration with external
> >> > authentication, easy to fix)
> >> > - extra permissions in the auth_permissions table (presumably I can
> >> correct
> >> > this by deleting no-longer-needed permissions flags)
> >> > - deleted users (I don't know how they were deleted, I don't have that
> >> > enabled! I can work-around this issue by re-adding "deleted" but
> >> inactive
> >> > users)
> >> >
> >> > ... I don't know what other problems I'll uncover, but I expect that
> >> I'll
> >> > uncover them. Before I go through that trial and error work, is there
> >> any
> >> > tool out there that will diagnose and potentially fix all the issues? I
> >> > know that 1.7.7.1 is a fairly old version (partly why I'm trying to
> >> bring
> >> > the darn thing current!), so I don't expect that someone has anything
> >> for
> >> > exactly this version - but perhaps for a later version, that I can
> >> adjust
> >> > for the older database schema?
> >> >
> >> > Thanks!
> >> >
> >> > Eric
> >> >
> >> > --
> >> > 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 "reviewboard"
> >> > group.
> >> > To unsubscribe from this group and stop receiving emails from it, send
> >> an email to reviewboard+unsubscr...@googlegroups.com.
> >> > For more options, visit https://groups.google.com/d/optout.
> >> >
> >>
> >> --
> >> 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
> >> "reviewboard" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an
> >> email to reviewboard+unsubscr...@googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >>
> >
>  
> --
> 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 
> "reviewboard"  
> group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to reviewboard+unsubscr...@googlegroups.com.  
> For more options, visit https://groups.google.com/d/optout.
>  

-- 
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 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to