1.4 Update of SMT From Previous Versions

This section contains the information about upgrading from the previous versions of SMT.

1.4.1 Update from Subscription Management Tool 11 SP2

There are two ways of upgrading SMT 11 SP2 to SMT 11 SP3:

  • Perform the on-line migration, using the wagon tool. For more information, refer to the general documentation for SUSE Linux Enterprise Server.

  • When upgrading SLES 11 to SP3 via booting the installation media, add the SMT add-on product. This will make sure that the SMT packages get updated together with SLES 11.

MySQL Database Migration

SLES11-SP3 introduces the upgrade of the MySQL database to version 5.5. This upgrade involves a change of the database format and the database needs to be converted accordingly.

After the MySQL database is upgraded, the database engine is not running. The database needs to be converted and MySQL started to continue using SMT. To migrate the MySQL database, run following commands as root:

touch /var/lib/mysql/.force_upgrade
rcmysql restart

We strongly recommend to back up the database before migrating it.

1.4.2 Update from Subscription Management Tool 10

In general, the update from SMT 10 is not supported. This is a list of issues that might occur if the update is performed:

Configuration Changes

Authentication of Access

There is a new optional value requiredAuthType in /etc/smt.conf to specify if authentication should be required to access the update repositories. If the value is not present in /etc/smt.conf, behavior is unchanged from SMT 10. See the SMT 11 manual for further details.

Registration URL Specific for SMT 11

SMT 11 does not use the registration URL from /etc/suseRegister.conf anymore, but reads the value [NU] NURegUrl from /etc/smt.conf. If the value is not present in /etc/smt.conf, the value from /etc/suseRegister.conf is used as a fallback.

Update of apache2 Configuration

The installed version of /etc/apache2/conf.d/nu_server.conf and /etc/apache2/conf.d/smt_mod_perl.conf will be replaced with a newer version.

Changes Related to Dropping Privileges by SMT Scripts

smt User

By default, all SMT scripts run under a new, unprivileged user named smt. The user can be defined in smt.conf.

Permissions of Files and Repositories

In SMT 10, all files and repositories were owned by root. In SMT 11, the smt user needs write access to these repositories. To fix up the permissions, use the changeSMTUserPermissions.sh script shipped as part of the SMT package.

Proxy Settings

The YaST proxy module writes the proxy information to /root/.curlrc. In SMT 11 the scripts are running with privileges dropped, therefore the .curlrc file in the home directory of the used user (smt by default) must be edited. Otherwise use smt.conf to define the proxy settings.