I have recovered The Foreman 1.13 following your advises. Thanks a lot Greg!
On Tuesday, October 25, 2016 at 11:50:58 PM UTC-7, Evgeny Vasilchenko wrote: > > Thanks a lot, Greg - I will try. > > On Tuesday, October 25, 2016 at 12:54:17 PM UTC-7, Greg Sutcliffe wrote: >> >> On 25 October 2016 at 20:05, Evgeny Vasilchenko <[email protected]> >> wrote: >> >>> I'm sure situation is not that bad - Foreman even sends audit email me >>> to once a day. >>> Need to figure out what can be done to database if anything. >>> >> >> Its not the actual database thats the issue, its that the code is too new >> (the first pending migration is in 1.11 - see [1]). >> >> One possibility is to grab a new VM, install 1.11 and point it at the >> production db and then run `foreman-rake db:migrate`. If that works, you >> can do the same with a 1.12 setup, and then run the 1.13 migrations on your >> production box. >> >> Good luck! >> Greg >> > -- 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.
