One important place to look at is provisioning templates. If you did some changes to them, you will need to reapply your changes after migration is complete. The templates were changed since 1.4, so you would have to manually merge your changes and the latest template.
On Tuesday, November 29, 2016 at 11:01:49 AM UTC+2, [email protected] wrote: > > I have inherited a Foreman 1.4 system running on Ubuntu Precise. I would > like to upgrade to the current Ubuntu LTS and current Foreman release. The > current installation uses a postgres database that is hosted on another > system. I do not want to try an in-place upgrade because I don't see a way > to test the upgrade. I have built a new database server. I have loaded the > current Foreman db on the new db server. I have also built a new Foreman > server and installed 1.14 on it, but when I attempt to migrate the database > 'foreman-rake db:migrate' konks over dead with: > > rake aborted! > ActiveRecord::RecordInvalid: Validation failed: Unable to turn on > websockets_encrypt, either websockets_ssl_key or websockets_ssl_cert is > missing > /usr/share/foreman/vendor/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:79:in > > `raise_record_invalid' > ... > > It there a simple solution to this problem? Is this a reasonable > approach? Should I install older versions of Foreman on the new server and > set through the upgrades? > > Thanks in advance for any pointers. > > Bill > -- 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.
