Thank you areyus and tbrisker,
I am going to take tbrisker’s advice and try to upgrade. The only issuer is that all the methods fail. I can’t even get anything higher than 1.2… Please help. I’m by no means a foreman expert. If you need more info, please let me know. I tried the following:
3.6 Upgrade
Upgrading to Foreman 1.3
Preparation
Before updating to 1.3, make sure you have successfully upgraded to 1.2 first.
Upgrading across more than one version is not supported, so it’s required to upgrade to each intermediate version and follow all upgrade instructions for the previous versions.
Please check the upgrade notes for this release, as there may be things to be aware of or additional steps:
Step 1 - Backup
It is recommended that you backup your database and modifications to Foreman files(config/settings.yaml, unattended installations etc). Most upgrades are safe but it never hurts to have a backup just in case.
For more information about how to backup your instance head over to Backuphttps://theforeman.org/manuals/1.3/index.html#5.5.1Backup
Step 2 - Perform the upgrade
Before proceeding, it is necessary to shutdown the Foreman instance.
Now it’s time to perform the actual upgrade. This process if different depending on how you downloaded Foreman. You only need to perform one of the following options.
Option 1 - Upgrading from a package on Fedora or RHEL
Upgrading from 1.2
Important note: Foreign keys on the SQL database level were introduced in the Foreman 1.3. During migration, all orphaned records are deleted automatically. It is strongly recommended to backup database prior proceeding with upgrade.
To upgrade an existing Foreman 1.2 installation, first update with the appropriate foreman-release package from the above list of release packages, e.g. for RHEL6
yum upgrade http://yum.theforeman.org/releases/1.3/el6/x86_64/foreman-release.rpm
cat /etc/yum.repos.d/foreman.repo.rpmnew > /etc/yum.repos.d/foreman.repo
Next upgrade all Foreman packages:
yum upgrade ruby* foreman*
If you wish to install the SELinux policy, also install the foreman-selinux package.
If Foreman doesn’t load due to a Passenger error (particularly referencing bundler_ext), verify the configuration against the description in the Software Collections sectionhttps://theforeman.org/manuals/1.3/index.html#3.3.2SoftwareCollections below.
You can skip to Step 3.
Option 2 - Upgrading from a package on Debian or Ubuntu
Upgrading from 1.2
Upgrading from 1.2 to 1.3 has been tested on both Debian and Ubuntu. Updating the packages will upgrade the application and automatically migrate the database.
apt-get update
apt-get dist-upgrade
You can skip to Step 3.
Option 3 - Downloaded release (tar.bz2)
- Uncompress the new program archive in a new directory.
- Copy your database settings-file config/database.yml into the new config directory.
- If your database is a simple file (e.g. SQLite), don’t forget to make it available in the new directory.
VERY IMPORTANT: do NOT overwrite config/settings.yml with the old one.
Option 4 - Upgrading from git
Please note now that the development branch has moved to Rails 3, you MUST take care to select a branch and make sure you get the correct one.
- Go to the Foreman root directory and run the following command:
For staying on the stable branch:
- git checkout 1.3-stable
- git pull
The following step is the one that could change the contents of your database. Go to your new Foreman directory (or the git dir), then migrate your database:
foreman-rake db:migrate
You should compile i18n strings and precompile assets now:
foreman-rake locale:pack
foreman-rake assets:precompile
Step 3 - Cleanup
Database should be migrated already, but you can make sure by executing the migration script again, it should produce no errors or output:
foreman-rake db:migrate
You should clear the cache and the existing sessions:
foreman-rake tmp:cache:clear
foreman-rake tmp:sessions:clear
Step 4 - Restart
Restart the application server (e.g. mongrel, thin, passenger)
Common issues
Thank you,
Mark S. Stone
Sr. Systems Engineer
IT Infrastructure Engineering
O 484.595.6310 M 267.768.0980
Mark.Stone@vertexinc.commailto:Mark.Stone@vertexinc.com
Vertex Inc.
2301 Renaissance Blvd.,
King of Prussia, PA 19406
www.vertexinc.comhttp://www.vertexinc.com/
[/uploads/default/original/2X/4/4e726411070b987f40762a5ec8b6b31e16768645.png]
LinkedInhttps://www.linkedin.com/company/vertex-inc./ | Facebookhttps://www.facebook.com/vertexinc1/ | Twitterhttps://twitter.com/vertexinc| Instagramhttps://www.instagram.com/lifeatvertex/?hl=en
You can mark a post as solution using the checkbox icon on the post that describes the solution.