HowToUpgrade17

Grant Gainey edited this page Dec 12, 2016 · 2 revisions
Clone this wiki locally

Spacewalk Upgrade Instructions

These are upgrade instruction for upgrading Spacewalk 1.6 to Spacewalk 1.7.

These upgrade instruction apply to Spacewalk installations meeting the following criteria:

  • Spacewalk 1.6 running on Red Hat Enterprise Linux 5 Server, 6 Server or CentOS 5 and CentOS 6 or Fedora 15.
  • Your Spacewalk uses either of Oracle 10g (including XE) / Oracle 11g / PostgreSQL 8.4+ as a database backend.

Archive of older upgrade instructions

  • Spacewalk 1.5 to 1.6 upgrade instructions, are available at HowToUpgrade16
  • Spacewalk 1.4 to 1.5 upgrade instructions, are available at HowToUpgrade15

Assumptions

  • For RHEL or CentOS, you will need the base and EPEL repositories enabled for dependencies.
  • For Fedora, your Fedora yum repositories are setup properly.
  • You had set up your yum to point to Spacewalk 1.7 repository. For the repo setup specifics, see HowToInstall#SettingupSpacewalkrepo.

Database and configuration backup

  • For existing configuration files, create a backup of everything under /etc/sysconfig/rhn /etc/rhn and /etc/jabberd
  • Backup your SSL build directory, ordinarily /root/ssl-build
  • For instructions on how to create a backup of your existing Spacewalk database consult either Oracle / PostgreSQL documentation or contact your DBA

Package upgrade

Your Spacewalk should be stopped at this point. Perform package upgrade using yum:

# yum clean all
# yum upgrade

During the upgrade, you may notice messages printed to the terminal when installing oracle-instantclient-selinux and spacewalk-selinux. These messages are produced by restorecon and do not pose any harm.

Check any .rpmnew/.rpmsave files that were created during the upgrade for your configuration files and make sure changes to your configuration files are preserved while new content from the distribution files is carried over.

# yum install rpmconf
# rpmconf -a

Schema upgrade

Make sure your Spacewalk server is down:

# /usr/sbin/spacewalk-service status

If you're using remote PostgreSQL database, make sure postgresql-contrib (or postgresql84-contrib for RHEL-5/CentOS 5) package is installed on the machine hosting your database server.

For RHEL-5 / CentOS 5:

rpm -q postgresql84-contrib

For RHEL-6 / CentOS 6 and Fedoras:

# rpm -q postgresql-contrib

If the /var/lib/pgsql/data/pg_hba.conf on your PostgreSQL server does not contain the line

local   all         all                               ident

from the default configuration, add line

local spaceschema postgres  ident

to the start of the file.

Make sure your database server is running. Run spacewalk-schema-upgrade script to upgrade database schema:

# /usr/bin/spacewalk-schema-upgrade

Important notes:

  • The above command will inform you whether or not was the schema upgrade successful.
  • Log files from schema upgrade are being put into /var/log/spacewalk/schema-upgrade.
  • Should the schema upgrade fail because of insufficient space in some of the tablespaces, restore the database from backup, extend the tablespaces as needed and execute this step again.

Upgrade of Spacewalk configuration

  1. Use spacewalk-setup to upgrade Spacewalk configuration. Run as root:
# spacewalk-setup --disconnected --upgrade
  1. Restore some of the custom values you might have set previously in /etc/rhn/rhn.conf from the backup of your configuration files, such as:
  • debug = 3
  • pam_auth_service = rhn-satellite
  1. Enable (or re-enable) monitoring (and monitoring scout).
  • If you wish to enable (or re-enable) monitoring without enabling monitoring scout, run the following command as root:

    /usr/share/spacewalk/setup/upgrade/rhn-enable-monitoring.pl

  • If you wish to enable (or re-enable) both monitoring and monitoring scout, run the following command:

    /usr/share/spacewalk/setup/upgrade/rhn-enable-monitoring.pl --enable-scout

Restart Spacewalk

# /usr/sbin/spacewalk-service start