Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

See What's New in Avalon 5.0 for more details.

Preparing for the Upgrade 

Before doing anything to prepare for the upgrade, back up your Avalon 4.0 installation.


The following instructions will work for any Avalon 4.0 installation that used Puppet as its source. This includes the portable VM Image Installation, the Vagrant Virtual Machine Installation, and the Manual Installation of Avalon Using Puppet Install.

Upgrading is fairly simple, and must be run as the root user from a bash prompt on the Avalon system. The process for this depends on which kind of installation you have.


  • Open a terminal window from within the VM console, and type su root to become the root user. This will require the root password you provided the first time the system was booted.
  • Vagrant virtual machine:
    From within the original installer directory (from step 4 of the Vagrant Virtual Machine Image Installation Instructions), type vagrant ssh to log in as the vagrant user, then type sudo -i to become the root user.
  • Manual Puppet installed machine:
    Log in and become root as you did in steps 1 and 2 of the Manual Installation of Avalon Using Puppet Install instructions.

Once you have a root prompt, proceed with the upgrade as follows:

Code Block
titleUpgrade Avalon
# 1. Upgrade ruby version to 2.2.5
$ rvm install 2.2.5
$ rvm use 2.2.5
$ yum update  

# 2. if starting from Portable VM image, download the installer package, unpack, and link it
$ wget -O flat.tar.gz 
$ tar xzf flat.tar.gz
$ export INSTALL_DIR=`pwd`
$ ln -s $INSTALL_DIR/avalon-installer-flat/files /etc/puppet/avalon_files

# 3. ensure avalon_files directory has RPM-GPG-KEY-avalon and ffmpeg 
$ ls /etc/puppet/avalon_files

# 4. navigate to the installer
$ cd avalon-installer-flat

# 5. remove the Avalon deploy tag
$ rm -f /var/www/avalon/bare-deploy
$ rm -rf /opt/staging/avalon/avalon-bare-deploy.tar.gz /opt/staging/avalon/avalon-bare-deploy
# 6. apply the puppet manifest
$ puppet apply --fileserverconfig=fileserver.conf --modulepath=modules \
	--hiera_config=hiera/hiera.yaml --templatedir=templates manifests/init.pp

# 7. reindex
$ su - avalon -c "cd /var/www/avalon/current; RAILS_ENV='production' bundle exec rake avalon:reindex"

Restart Delayed Job

See details here: Restart Delayed Job

Sample Content

If you didn't load the sample content before, try it out to test your avalon 5.0 upgrade.