Skip to content
This repository has been archived by the owner on Jun 3, 2020. It is now read-only.

HowToUpgrade27

Jump to bottom
Eric Herget edited this page Sep 29, 2017 · 4 revisions

Spacewalk Upgrade Instructions

These are upgrade instructions for upgrading Spacewalk 2.6 to Spacewalk 2.7

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

  • Spacewalk 2.6 running on Red Hat Enterprise Linux/CentOS/Scientific Linux 6/7 Server, or Fedora 24.
  • Your Spacewalk uses one of Oracle 10g (including XE) / Oracle 11g / PostgreSQL 8.4+ as a database backend.
  • In most cases it's possible to perform Package upgrade and Schema upgrade steps from any previous version to the latest one directly (e.g. from 1.6 to 2.6). However in the transition from 2.6 to 2.7, there are package dependency changes that must be accounted for. Make sure you have a valid backup in case anything will go wrong.

Archive of older upgrade instructions

  • Spacewalk 2.5 to 2.6 upgrade instructions, are available at HowToUpgrade26
  • Spacewalk 2.4 to 2.5 upgrade instructions, are available at HowToUpgrade25
  • Spacewalk 2.3 to 2.4 upgrade instructions, are available at HowToUpgrade24
  • Spacewalk 2.2 to 2.3 upgrade instructions, are available at HowToUpgrade23
  • Spacewalk 2.1 to 2.2 upgrade instructions, are available at HowToUpgrade22
  • Spacewalk 2.0 to 2.1 upgrade instructions, are available at HowToUpgrade21
  • Spacewalk 1.9 to 2.0 upgrade instructions, are available at HowToUpgrade20
  • Spacewalk 1.8 to 1.9 upgrade instructions, are available at HowToUpgrade19
  • Spacewalk 1.7 to 1.8 upgrade instructions, are available at HowToUpgrade18
  • Spacewalk 1.6 to 1.7 upgrade instructions, are available at HowToUpgrade17
  • Spacewalk 1.5 to 1.6 upgrade instructions, are available at HowToUpgrade16

Assumptions

  • For RHEL, CentOS, or Scientific Linux, you have the base-OS and EPEL repositories enabled.
  • For RHEL, you have the appropriate 'Optional Server' channel enabled.
  • For Fedora, your Fedora yum repositories are setup properly.
  • You have set up your yum to point to Spacewalk 2.7 repository. For the repo setup specifics, see HowToInstall#setting-up-spacewalk-repo.

Special Note For Those Who Will Manage Debian/Ubuntu Clients

There is a change that will need to be made to Debian/Ubuntu client systems. There are also additional steps to take after upgrading to Spacewalk 2.7. For more details see DebianUbuntuSupportIn27

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
  • BACKUP YOUR DATABASE. For instructions on how to create a backup of your existing Spacewalk database consult either Oracle / PostgreSQL documentation or contact your DBA

Package upgrade

Lock versions

When running on Fedora 24, you may need to lock the versions of several third-party libraries prior to upgrading, due to changes in the Fedora repositories. Execute the following commands:

# dnf install python3-dnf-plugin*-versionlock
# echo 'quartz-1.8.4' >>/etc/dnf/plugins/versionlock.list

When running on RHEL7, Scientific Linux 7, CentOS 7, you may consider revising your current version-locked packages and remove them as needed. In particular, cglib and c3p0 no longer need to be locked.

# yum versionlock list
# yum versionlock delete cglib c3p0

Remove conflicting packages

When running on RHEL6, Scientific Linux 6, CentOS 6, you need to remove certain packages formerly installed from jpackage repo which are not used anymore and cause dependency conflicts. Execute the following command:

# rpm -e --nodeps  axis-*-*.jpp5 jakarta-commons-logging-*-*.jpp5 jakarta-commons-digester-*-*jpp jakarta-commons-dbcp-*-*.jpp5 jakarta-commons-discovery-*-*.jpp5 java-cup-*-*.jpp5 junit-*-*.jpp5 wsdl4j-*-*.jpp5 xalan-j2-*-*.jpp5

All systems

Perform package upgrade using yum:

# 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
# /usr/sbin/spacewalk-service stop

On a systemd supported system, reload the systemd manager configuration:

# systemctl daemon-reload

Do a backup of your database. (No, really - go do that. We'll wait.)

If you are running PostgreSQL database backend check whether you have created language pltclu:

su - postgres -c "PGPASSWORD=spacepw; createlang pltclu $(spacewalk-cfg-get db_name) ;"

If you are running Oracle database backend grant these rights to your database user:

Update spacewalk database user - replace with your database user name

# sqlplus 'sys/<password>@//localhost/XE as sysdba' 
SQL> grant create table to <spacewalk>; 
SQL> grant create trigger to <spacewalk>; 
SQL> quit

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 the schema upgrade was successful.
    • Log files from schema upgrade are stored in /var/log/spacewalk/schema-upgrade.
    • Should the schema upgrade fail, investigate, restore from backup, fix the cause (for example, if it failed because of insufficient space in tablespace, extend the tablespaces) and rerun spacewalk-schema-upgrade.

Upgrade of Spacewalk configuration

  1. Use spacewalk-setup to upgrade Spacewalk configuration.

If you are using the default database setup, run:

# spacewalk-setup --upgrade

If you are using an external database, then run

# spacewalk-setup --external-$DB --upgrade

where DB will be either oracle or postgresql, depending on what your external database is.

  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

Restart Spacewalk

If you are running Spacewalk on Fedora run following command before starting Spacewalk services

systemctl daemon-reload

Then, start all Spacewalk services:

# /usr/sbin/spacewalk-service start

Known Issues

Tomcat on RHEL 6 fails to start

On RHEL6 tomcat may fail to restart with the following message in the /var/log/tomcat6/catalina.out:

SEVERE: Error deploying configuration descriptor rhn.xml
java.lang.IllegalStateException: ContainerBase.addChild: start: LifecycleException:  start: :  java.io.IOException: Failed to access resource /WEB-INF/lib/jta.jar

This issue is caused by yum which removed symlink /usr/share/java/jta.jar. To fix it run:

# ln -s geronimo-jta.jar /usr/share/java/jta.jar

And then restart tomcat6 again:

# service tomcat6 restart

Tomcat on RHEL 7 / CentOS 7 fails to start

On RHEL 7, Scientific Linux 7, CentOS 7, Tomcat package RHN may fail to start with the following message in /var/log/tomcat/localhost.yyyy-mm-dd:

spacewalk 2.7 Unsupported major.minor version 52.0 (unable to load class EDU.oswego.cs.dl.util.concurrent.Channel)

This issue may be caused by incorrect default Java version. Spacewalk 2.7 no longer requires Java 1.7:

# java -version 
# alternatives --list

To fix, ensure that Java 1.8 is being used by default. If possible, consider uninstalling Java 1.7 altogether:

# yum install -y java-1.8.0-openjdk-devel
# yum erase java-1.7.0-openjdk java-1.7.0-openjdk-devel java-1.7.0-openjdk-headless

And then restart Spacewalk services.

Do you want to contribute to this wiki? See page WikiContribute for more info.

Help

Documentation

Clone this wiki locally