> > I'd suggest editing > /usr/share/foreman/db/migrate/20140304184854_add_provision_method_to_hosts.rb > > and commenting out the "remove_column" line with a #, then run: > > foreman-rake db:migrate:down VERSION=20140304184854 > foreman-rake db:migrate:up VERSION=20140304184854 >
Yep, this certainly fixed my problem - thank you very much, Dominic! While we are on this topic - is there a reason why all of those files under /usr/share/foreman/db/migrate cannot be used for DB migration steps to allow Foreman admins to "jump" the major releases? Since I personally just when through that exercise to go from 1.7.1 to 1.13.0, I can assure you that it was a rather major pain of figuring out all of the repo and package dependencies and such just to install foreman packages of intermediate versions (1.8, 1.9, 1.10, then move to a different centos7 host to proceed with 1.11 to 1.12 and then to 1.13) and running "foreman-rake db:migrate; foreman-rake db:seed"... (shrugs) I'd rather have a new centos7 with 1.13.0 installed, then import a DB dump from 1.7.1 and run all the db:migrate steps in between 1.7.1 to my desired version minus one (so 1.12.3 in this particular case) and finish this up with regular "foreman-rake db:migrate; foreman-rake db:seed" sequence. Is that possible? Would it be just as simple as figuring out the db-migrate versions in between and applying them with above procedure one by one? Please let me know your thoughts. Having some procedure to simply that process would be such a big help as not every time it is possible/feasible to keep on upgrading Foreman just for the sake of staying close to the latest version. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
