From 7f754d0deeb121bb0a4c4d294459c413800d7ffa Mon Sep 17 00:00:00 2001 From: petervreeburg Date: Fri, 21 Sep 2018 13:05:38 +0200 Subject: [PATCH] Update 3.6_Update.md with findings During upgrade of 1.18 to 1.19, some issues did pop up, described in https://community.theforeman.org/t/issues-during-upgrade-1-18-2-to-1-19-following-the-upgrade-guide/11158 Added some small notes to make sure future upgrades may not suffer from this issue. --- _includes/manuals/1.19/3.6_upgrade.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/_includes/manuals/1.19/3.6_upgrade.md b/_includes/manuals/1.19/3.6_upgrade.md index aa854c29bc..ebb323d924 100644 --- a/_includes/manuals/1.19/3.6_upgrade.md +++ b/_includes/manuals/1.19/3.6_upgrade.md @@ -74,7 +74,8 @@ number from the previous release or "stable" to `{{ page.version }}`: deb http://deb.theforeman.org/ stretch {{ page.version }} deb http://deb.theforeman.org/ plugins {{ page.version }} -Next upgrade all Foreman packages: +Next upgrade all Foreman packages. +During the upgrade it's suggested to update the /etc/foreman/database.yml to the package version. If you used foreman-installer to setup your existing Foreman instance, make sure not to upgrade this file with the version from the package. apt-get update apt-get --only-upgrade install ruby\* foreman\* @@ -126,7 +127,7 @@ You should compile i18n strings and precompile assets now: ##### Step 3 (A) - Database migration and cleanup The database should be migrated already, but you can make sure by executing the -migration script again, it should produce no errors or output: +migration script again, it should produce no errors or output. If you used foreman-installer to setup your existing Foreman instance, you can skip this step and jump over to step 3(C): foreman-rake db:migrate foreman-rake db:seed