We have no back up of this VM due to stupid coincidence of various factors. A backup did exists, but was accidentally overwritten by a newer version. :(
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. I just have no time to fix this now, but company is okay to hire an expert and try to fix it. I can deploy 1.13 from scratch, but just recovering all customization done in Foreman is a bit of pain. Thanks! On Tuesday, October 25, 2016 at 11:08:25 AM UTC-7, Greg Sutcliffe wrote: > > On 24 October 2016 at 18:06, Evgeny Vasilchenko <[email protected] > <javascript:>> wrote: > >> Please anyone? Any suggestions beside of 1.10 backup restore? >> > > I think there's a few points here: > > 1) Oracle Linux isn't officially supported - that's probably not the > problem, but it's worth remembering > 2) If the system crashed during a db:migrate (which is called by the > packages during upgrade) then it's could well be in an inconsistent state > 3) Direct upgrades skipping major releases are known to break - the > migrations care what version of the code they invoke. > > Of these, I suspect (3) is your issue. A undefined method suggests that > you've skipped a major version - assuming you have backups, your best > option is a rollback followed by a 1.10->1.11->1.12->1.13 upgrade. > > 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.
