space walk

Spacewalk 2.2 for Oracle Linux 6Release Notes

E58680-02February 2015

About this document

This document contains information about the Spacewalk 2.2 release available from Oracle. It describes thedifferences from the upstream version, includes notes on installing and configuring Spacewalk, and provides astatement of what is supported.

For legal information, see Oracle Legal Notices.

Document generated on: 2015-02-06 (revision: 2561)

iii

Table of ContentsPreface .............................................................................................................................................. v1 Release Notes ................................................................................................................................ 1

1.1 About Spacewalk 2.2 for Oracle Linux 6 ............................................................................... 11.2 Installing and Upgrading Spacewalk ...................................................................................... 1

1.2.1 Oracle Linux Requirements ........................................................................................ 11.2.2 Database Requirements ............................................................................................ 21.2.3 Storage Requirements ............................................................................................... 31.2.4 Network Requirements .............................................................................................. 31.2.5 Installing Spacewalk .................................................................................................. 31.2.6 Upgrading Spacewalk to Release 2.2 ......................................................................... 5

1.3 Configuring Spacewalk ......................................................................................................... 71.3.1 Configuring Software Channels Using ULN ................................................................. 81.3.2 Configuring Software Channels Using Public Yum ....................................................... 81.3.3 Synchronizing Software Channels .............................................................................. 91.3.4 Creating Activation Keys for Spacewalk Clients ......................................................... 10

1.4 Installing the Spacewalk Client and Registering Servers ....................................................... 111.5 Known Issues .................................................................................................................... 12

1.5.1 Spacewalk Fails to Install Due to slf4j Package ..................................................... 121.5.2 Tomcat Fails to Start After Spacewalk Configuration .................................................. 121.5.3 Spacewalk Client Fails to Install on Oracle Linux 5 .................................................... 131.5.4 Oracle Linux 5 Does Not Register with Spacewalk after Kickstart Installation ............... 131.5.5 PXE Booting Fails Due to Incorrect Host Name Configuration .................................... 131.5.6 Out of Memory Issues With Large Repositories or Data Sets ...................................... 131.5.7 Client Registration Issues ........................................................................................ 131.5.8 Clients Have to Prerequisite After an Upgrade .......................................................... 131.5.9 Issues With Kickstart After an Upgrade, .................................................................... 14

A Legal Notices ............................................................................................................................... 15A.1 Oracle Legal Notices ......................................................................................................... 15A.2 DocBook XSL License ....................................................................................................... 16

vPrefaceThe Spacewalk 2.2 for Oracle Linux Release Notes provides details of the Spacewalk 2.2 release availablefrom Oracle.

Audience

This document is written for system administrators who want to use Spacewalk to manage Oracle Linuxsystems. It is assumed that readers have a general understanding of the Linux operating system.

Conventions

The following text conventions are used in this document:

Convention Meaningboldface Boldface type indicates graphical user interface elements associated with an

action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which

you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in

examples, text that appears on the screen, or text that you enter.

1Chapter 1 Release Notes1.1 About Spacewalk 2.2 for Oracle Linux 6

There are no significant changes in the Oracle version of Spacewalk from the upstream project.Minor changes include the addition of Oracle Linux 6 GPG keys and some branding changes.

Summary of New Features and Changes Since Release 2.0In addition to numerous fixes and small enhancements, the Spacewalk 2.2 release includes the followingnew features and changes:

New design for the web interface.

Support for defining a chain of actions to be executed on clients (action chaining). Remote power management.

Support for FIPS-enabled Spacewalk clients and servers.

Spacewalk Proxy content pre-caching.

Identity management (IPA) integration. Support for using SSL for connections to an external PostgreSQL database.

SCAP improvements.

New API calls and a new read-only user API for retrieving data, for example for auditing.

The up-to-date API documentation can be found at: http://www.spacewalkproject.org/documentation/api/ The Monitoring component of Spacewalk is deprecated and might not be available in future Spacewalk

releases. If you have already deployed this component, it is still supported but you should investigatealternative monitoring solutions.

Detailed information about the changes can be found in the Release Notes for the Spacewalk project at:https://fedorahosted.org/spacewalk/wiki/ReleaseNotes

1.2 Installing and Upgrading Spacewalk1.2.1 Oracle Linux Requirements

Spacewalk provided by Oracle is only supported on Oracle Linux 6 (x86_64).You should install Oracle Linux 6 using the Minimal or Basic Server software set. If you select additionalpackage groups during installation, you must remove the jta package before installing Spacewalk, as thispackage causes Spacewalk services to fail to start.

Only install Spacewalk using the packages provided by Oracle from the Oracle Public Yum repository athttp://public-yum.oracle.com.

No thirdparty package repositories are required to install Spacewalk on Oracle Linux 6. All the requiredpackages are available in the Oracle Linux Spacewalk repository.

Database Requirements

2

As a minimum, a Spacewalk server should have 8GB RAM. If the Spacewalk server also runs thedatabase for the Spacewalk data, this memory requirement is in addition to what is required to run thedatabase.

1.2.2 Database RequirementsA database is required to store the Spacewalk data. The database options are:

Oracle Database

Oracle Database Express Edition (Oracle Database XE) PostgreSQL

Oracle only supports Oracle Database for use with Spacewalk. Oracle Database XE and PostgreSQL arenot supported.

Oracle does not provide any tools for migrating from an unsupported database. For information onsetting up a PostgreSQL database for use with Spacewalk, see https://fedorahosted.org/spacewalk/wiki/PostgreSQLServerSetup.

Oracle Database RequirementsYou must have an Oracle Database server installed and available before you install Spacewalk.

Only Oracle Database 11gR2, release 11.2.0.3 or later, is supported. Oracle Database 12c is notsupported. To obtain the correct Oracle Database 11gR2 release, you must download the software fromMy Oracle Support (MOS) at https://support.oracle.com.Documentation for Oracle database is available at https://docs.oracle.com/en/database/database.html.

The database must be configured as follows:

The database must use the AL32UTF8 character set.

The database must have a user named spacewalk.

The spacewalk user must have the CONNECT and RESOURCE roles.

The spacewalk user must have the ALTER SESSION, CREATE SYNONYM, CREATE TABLE, CREATETRIGGER, CREATE VIEW and UNLIMITED TABLESPACE system privileges.

To create the spacewalk user with a password of "password" using SQL, the following SQL*Pluscommands can be used:SQL> create user spacewalk identified by password;SQL> grant connect,resource to spacewalk;SQL> grant alter session, create synonym, create table, create trigger, create view to spacewalk; SQL> grant unlimited tablespace to spacewalk;

To connect to an Oracle Database, Oracle Instant Client release 11.2.0.3 or later must be installed onthe Spacewalk server. The Spacewalk server configuration fails if the Instant Client is missing. Oraclerecommends that you install the latest 11gR2 release of the Instant Client. You can download the InstantClient from:

http://www.oracle.com/technetwork/topics/linuxx86-64soft-092277.html

The following are the required packages:

Instant Client Package - Basic

Storage Requirements

3

Instant Client Package - SQL*Plus

Once you have installed the Oracle Instant Client, you must add the library path to ldconfig as follows:

# echo /usr/lib/oracle/11.2/client64/lib > /etc/ld.so.conf.d/oracleinstantclient11.2.conf # ldconfig

1.2.3 Storage RequirementsTo ensure that errata mapping is maintained for all versions of each package, Spacewalk mirrors allavailable versions of all available packages. As a result, the storage requirements for a Spacewalk servercan be significant, based on the number of major versions and architectures you chose to support. As aguide, the Oracle Linux binary repositories require approximately 50GB for each architecture, with an extra30-40GB required for source packages.

Caution

Packages are never removed from Oracle Linux repositories, so the space requiredfor each repository only ever increases. You should actively monitor the availabledisk space on the Spacewalk server.

1.2.4 Network RequirementsYou must configure the Spacewalk server with a fully-qualified domain name (FQDN). Spacewalk doesnot consider .local and .localdomain to be valid domain names. Clients must be able to resolve theFQDN in DNS (forward and reverse lookups). If these conditions are not met, PXE booting does not workand clients do not register with the Spacewalk server.

The following table shows the required network ports depending on the configuration of the Spacewalkserver.

Port and Protocol Purpose69/udp tftp for PXE provisioning support80/tcp Spacewalk web access443/tcp Spacewalk web access5222/tcp Spacewalk client push support5269/tcp Spacewalk proxy push support

If the Spacewalk server needs to connect though a proxy, you can configure the proxy in the followingplaces:

The /etc/rhn/rhn.conf file.

The Spacewalk web interface.

Go to Overview, then Configure Spacewalk, and then General.

1.2.5 Installing Spacewalk1. Ensure that the jta package is not installed and prevent it from being installed when you install

Spacewalk.

To check if the jta package is installed:# yum list installed | grep jta

Installing Spacewalk

4

To remove the jta package:# yum remove jta

To prevent the jta package from being installed when you install Spacewalk, either disable the OracleLinux 6 Add ons [ol6_addons] channel, or add the jta package to the exclude directive in the yumconfiguration file /etc/yum.conf, for example:exclude=jta*

2. Enable access to the Spacewalk 2.2 Server repository.

Spacewalk is installed from the Oracle Public Yum server at http://public-yum.oracle.com.

Download the latest the Oracle public yum repository configuration file (http://public-yum.oracle.com/public-yum-ol6.repo) to the yum repositories directory (by default /etc/yum.repos.d) and enable theol6_spacewalk22_server repository in that file.

Alternatively, you can create a yum repository configuration file, for example /etc/yum.repos.d/spacewalk22.repo, with the following content:[ol6_spacewalk22_server]name=Spacewalk Server 2.2 for Oracle Linux 6 ($basearch)baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/spacewalk22/server/$basearch/gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oraclegpgcheck=1enabled=1

3. Install Spacewalk.

If you are using an Oracle database:# yum install spacewalk-oracle

If you are using a PostgreSQL database:# yum install spacewalk-postgresql

You can safely ignore any SELinux restorecon messages that are displayed when the packages areinstalled.

4. Configure Spacewalk.

If you are using an Oracle database, either on the same server or on a remote server, use the followingcommand:# spacewalk-setup --disconnected --external-oracle

Otherwise, use the following command:# spacewalk-setup --disconnected

The following example shows an interactive configuration:# spacewalk-setup --disconnected --external-oracle * Setting up Oracle environment. * Setting up database. ** Database: Setting up database connection for Oracle backend. Database service name (SID)? orcl.domain.com Database hostname [localhost]? spacewalk-db.domain.com Username? spacewalk

Upgrading Spacewalk to Release 2.2

5

Password? ** Database: Testing database connection. ** Database: Populating database. *** Progress: ############################################################ * Setting up users and groups. ** GPG: Initializing GPG and importing key. ** GPG: Creating /root/.gnupg directory You must enter an email address. Admin Email Address? [email protected] * Performing initial configuration. * Activating Spacewalk. ** Loading Spacewalk Certificate. ** Verifying certificate locally. ** Activating Spacewalk. * Enabling Monitoring. * Configuring apache SSL virtual host. Should setup configure apache's default ssl server for you (saves original ssl.conf) [Y]? y ** /etc/httpd/conf.d/ssl.conf has been backed up to ssl.conf-swsave * Configuring tomcat. ** /etc/sysconfig//tomcat6 has been backed up to tomcat6-swsave ** /etc/tomcat6//server.xml has been backed up to server.xml-swsave ** /etc/tomcat6//web.xml has been backed up to web.xml-swsave * Configuring jabberd. * Creating SSL certificates. CA certificate password? Re-enter CA certificate password? Organization? Oracle Demo Organization Unit [spacewalk.domain.com]? spacewalk.domain.com Email Address [[email protected]]? [email protected] City? Redwood Shores State? CA Country code (Examples: "US", "JP", "IN", or type "?" to see a list)? US ** SSL: Generating CA certificate. ** SSL: Deploying CA certificate. ** SSL: Generating server certificate. ** SSL: Storing SSL certificates. * Deploying configuration files. * Update configuration in database. * Setting up Cobbler.. Processing /etc/cobbler/modules.conf `/etc/cobbler/modules.conf' -> `/etc/cobbler/modules.conf-swsave' Processing /etc/cobbler/settings `/etc/cobbler/settings' -> `/etc/cobbler/settings-swsave' cobblerd does not appear to be running/accessible Cobbler requires tftp and xinetd services be turned on for PXE provisioning functionality. Enable these services [Y]? y cobblerd does not appear to be running/accessible * Restarting services. Installation complete. Visit https://spacewalk.domain.com to create the Spacewalk administrator account.

5. Go to the Spacewalk server and create the Spacewalk administrator account.

1.2.6 Upgrading Spacewalk to Release 2.21. Back up your Spacewalk configuration files.

Create a backup of everything in the following directories:

/etc/sysconfig/rhn

/etc/rhn

/etc/jabberd

/root/ssl-build (or wherever your server SSL build directory is located)

Upgrading Spacewalk to Release 2.2

6

2. Back up your Spacewalk database.

See the documentation for your database for instructions on how to create a backup.

3. Disable access to the Spacewalk 2.0 Server repository and enable access to the Spacewalk 2.2 Serverrepository.

Disable Spacewalk 2.0 Server repository in the Oracle public yum repository configuration file, or deleteyour Spacewalk 2.0 Server .repo file.

Spacewalk 2.2 is installed from the Oracle Public Yum server at http://public-yum.oracle.com.

Download the latest the Oracle public yum repository configuration file (http://public-yum.oracle.com/public-yum-ol6.repo) to the yum repositories directory (by default /etc/yum.repos.d) and enable theol6_spacewalk22_server repository in that file.

Alternatively, you can create a yum repository configuration file, for example /etc/yum.repos.d/spacewalk22.repo, with the following content:[ol6_spacewalk22_server]name=Spacewalk Server 2.2 for Oracle Linux 6 ($basearch)baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/spacewalk22/server/$basearch/gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oraclegpgcheck=1enabled=1

4. Upgrade the Spacewalk packages using yum upgrade.

You can safely ignore any SELinux restorecon messages that are displayed when the packages areinstalled.

5. Install the rpmconf package and use the rpmconf command to copy any customizations you want topreserve to the upgraded configuration files.

# yum install rpmconf# rpmconf -a

6. Stop the Spacewalk service.

# /usr/sbin/spacewalk-service stop# /usr/sbin/spacewalk-service status

7. Upgrade the Spacewalk database schema.

a. Make sure the database server is running.

If you are using the embedded PostgreSQL database, the spacewalk-service stop commandstops the postgresql service. To start the service, run the following command:# service postgresql start

b. (PostgreSQL database only) Run the following commands to create the pltclu language:

# /usr/bin/spacewalk-cfg-get db_namerhnschema# su - postgres -c 'PGPASSWORD=; createlang pltclu ;'

c. (Oracle database only) Grant additional rights to the Spacewalk database user:

Configuring Spacewalk

7

SQL> grant create table to spacewalk; SQL> grant create trigger to spacewalk;

d. Upgrade database schema.

# /usr/bin/spacewalk-schema-upgrade

The output of the spacewalk-schema-upgrade command confirms whether or not the schemaupgrade was successful. In the event of a failure:

Check the log files in the /var/log/spacewalk/schema-upgrade directory to establish thecause.

Restore the database from the backup.

Fix the cause of the problem, for example by extending the tablespaces if there is insufficientspace.

Upgrade the database schema.

8. Upgrade the Spacewalk configuration.

If you are using an Oracle database:

# spacewalk-setup --disconnected --external-oracle --upgrade

If you are using a PostgreSQL database:# spacewalk-setup --disconnected --external-postgresql --upgrade

If you have customized the Spacewalk installation, for example in /etc/rhn/rhn.conf, restore thecustomizations from your backup.

9. (Optional) Enable monitoring and the monitoring scout.To enable monitoring without enabling the monitoring scout:

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

To enable monitoring and the monitoring scout:

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

10. Restart Spacewalk

# /usr/sbin/spacewalk-service start

1.3 Configuring SpacewalkThis section describes the configuration needed to enable Spacewalk to synchronize software with OracleUnbreakable Linux Network (ULN) or the Oracle public yum server. Detailed user documentation for theSpacewalk project can be found at:https://fedorahosted.org/spacewalk/wiki/UserDocs

Configuring Software Channels Using ULN

8

1.3.1 Configuring Software Channels Using ULNSpacewalk contains a ULN plug-in for the spacewalk-repo-sync tool. The plugin enables you tosynchronize ULN channels directly into Spacewalk channels without requiring the Spacewalk server to beregistered with ULN.

To configure the ULN plug-in, edit the /etc/rhn/spacewalk-repo-sync/uln.conf file and add logincredentials for ULN. By default, this file is read-only by root.

[main] username = password =

After you edit the configuration file, ensure that the file permissions are read-only (0400) by root. This isan important security step to protect the ULN credentials.

Once the ULN plug-in is configured, you create the Spacewalk software channels and repositories in thenormal way using the Spacewalk web interface. When you specify the URL for a ULN repository, use aURL in the following format:

uln:///

Note

The URL must contain three forward slash (/) characters. For example:uln:///ol6_x86_64_latest

You can get a list of available ULN channel labels by logging in to ULN (https://linux.oracle.com) andselecting the Channels tab.

1.3.2 Configuring Software Channels Using Public YumOracle Linux channels can be configured using the spacewalkcommonchannels tool provided in thespacewalkutils package. This tool can automatically configure the required software channels, publicyum repositories, GPG keys, and activation keys for Oracle Linux.

The following channels can be created using the spacewalk-common-channels command:

For Oracle Linux 7 (x86_64):oraclelinux7 (base channel)oraclelinux7-optional

oraclelinux7-addons

oraclelinux7-uek-r3

oraclelinux7-mysql55

oraclelinux7-mysql56

oraclelinux7-spacewalk22-client

For Oracle Linux 6 (i386 and x86_64):oraclelinux6 (base channel)

Synchronizing Software Channels

9

oraclelinux6-addons

oraclelinux6-uek

oraclelinux6-uek-r3

oraclelinux6-mysql

oraclelinux6-playground


oraclelinux6-spacewalk20-server


oraclelinux6-spacewalk22-server

For Oracle Linux 5 (i386 and x86_64):oraclelinux5 (base channel)oraclelinux5-addons

oraclelinux5-oracle-addons

oraclelinux5-unsupported

oraclelinux5-uek



For example, to create all the 32bit and 64bit software channels for Oracle Linux 6, install thespacewalkutils package and then run the spacewalkcommonchannels tool, as follows:

# yum install spacewalkutils # spacewalkcommonchannels -v -u -p -a i386,x86_64 -k unlimited oraclelinux6*

Use the spacewalkcommonchannels -h command to see full usage information.

1.3.3 Synchronizing Software ChannelsOnce you have configured the software channels, you can synchronize the software either by performingan immediate manual synchronization or by scheduling a recurring synchronization job.

As a minimum, Oracle recommends that you update the Oracle Linux latest channels daily.

The initial synchronization of the Oracle Linux channels can take several days to complete. Oraclerecommends that you perform an initial manual synchronization to populate the channels, and thenconfigure a recurring job to keep them updated.

Synchronizing Software Channels Using the Spacewalk Web Interface1. Go to Channels, then Manage Software Channels, and select the required channel.

Creating Activation Keys for Spacewalk Clients

10

2. Select Repositories, and then Sync.

3. Synchronize the software.

To perform an immediate manual synchronization, click the Sync Now button.

To schedule a recurring synchronization job, select the preferred schedule, and click the Schedulebutton.

Synchronizing Software Channels Using the Command Line

Use the spacewalk-repo-sync tool to synchronize software channels. You must be root to use thistool. You can run the tool manually or in a cron job. See the man page for spacewalk-repo-sync forfull details of the options. If you run the tool in a cron job, remember to include the -q or --quiet option.

In order to synchronize a channel, the key information is the channel label and the URL of the repository.Use the spacewalk-repo-sync -l command to display this information.

To synchronize a channel with a ULN repository, use the following format:

# spacewalk-repo-sync -t uln -c -u uln:///

For example:

# spacewalk-repo-sync -t uln -c oraclelinux6_x86_64_latest -u uln:///ol6_x86_64_latest

To synchronize a channel with an Oracle Public Yum repository, use the following format:

# spacewalk-repo-sync -c -u http://

For example:

# spacewalk-repo-sync -c oraclelinux6_x86_64_latest \-u http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/

1.3.4 Creating Activation Keys for Spacewalk ClientsAfter you have configured and synchronized the software channels, you must create an activation key sothat servers can register to those channels.

Create an activation key for each base channel and architecture you configured. If you configure all thebase channels, you need five activation keys, two for Oracle Linux 5 (i386 and x86_64), two for OracleLinux 6 (i386 and x86_64), and one for Oracle Linux 7 (x86_64).

You synchronize software as follows:

1. In the Spacewalk web interface, go to Systems, and then Activation Keys.

2. Click Create New Key.

Oracle recommends that you enter a meaningful label for the activation key in the Key field and thatyou do not use automatic key generation.

Create a key with a label that is easy to understand, for example based on the version number andarchitecture (oraclelinux6-x86_64), or based on the server type (webserver or appserver).Spacewalk automatically adds a number to the activation key label.

Installing the Spacewalk Client and Registering Servers

11

For example, if you select oraclelinux-x86_64 as the label, the key that is actually created mightbe called 1-oraclelinux-x86_64. This enables you to create multiple activation keys for thesame base channel, each with different configuration options. The name you use is presented duringSpacewalk client registration and creating your own key labels helps you to select the right key.

1.4 Installing the Spacewalk Client and Registering ServersOracle supports only Oracle Linux servers as Spacewalk clients. Other client platforms, such as Fedora,can connect to Spacewalk but they are not supported.

Oracle provides Spacewalk client packages for Oracle Linux 5 and 6 for both i386 and x86_64architectures. For Oracle Linux 7, only packages for the x86_64 architecture are provided.

If the Spacewalk Client channel provided by Oracle is mirrored on the Spacewalk server, the Spacewalkclient is installed automatically on servers that are provisioned from Spacewalk. The Spacewalk Clientchannel can be configured using the spacewalk-common-channels command, as described inSection 1.3.2, Configuring Software Channels Using Public Yum.

For an Oracle Linux server that is not yet connected to Spacewalk, you install the Spacewalk client andregister the server, as follows:

1. Enable access to the Spacewalk Client repository.

Download the latest the Oracle public yum repository configuration file from http://public-yum.oracle.com/ and save it to the yum repositories directory (by default /etc/yum.repos.d). Editthe configuration file and enable the repository:

Oracle Linux 7: enable the ol7_spacewalk22_client repository.

Alternatively, you can create a /etc/yum.repos.d/spacewalk22-client.repo file with thefollowing content:

[ol7_spacewalk22_client]name=Spacewalk Client 2.2 for Oracle Linux 7 ($basearch)baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL7/spacewalk22/client/$basearch/gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oraclegpgcheck=1enabled=1



[ol6_spacewalk22_client]name=Spacewalk Client 2.2 for Oracle Linux 6 ($basearch)baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/spacewalk22/client/$basearch/gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oraclegpgcheck=1enabled=1



[ol5_spacewalk22_client]name=Spacewalk Client 2.2 for Oracle Linux 5 ($basearch)

Known Issues

12

baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/spacewalk22/client/$basearch/gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oraclegpgcheck=1enabled=1

2. (Oracle Linux 5 only) Remove the pirut, up2date, and up2dategnome packages.Use the rpm -e --nodeps command to remove these packages.

In your Oracle Linux 5 Kickstart profiles in Spacewalk, exclude these packages from installation byinserting a dash character (-) in front of the package name in the Kickstart profile on the Software,Package Group screen, for example:@Base-pirut-up2date-up2date-gnome

3. Install the Spacewalk client.

Use the following command to install the Spacewalk client on all platforms:# yum install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin

This command replaces the existing packages and deletes a registered server from ULN.

4. Register the server with Spacewalk using the rhnreg_ks command.

Before you can register a server, you must have already created a client activation key, as described inSection 1.3.4, Creating Activation Keys for Spacewalk Clients. If enabled, a universal default key canbe used. However, using a specific activation key is better.

You can use the rhn_register command to register a server with Spacewalk but this command doesnot use an activation key. If you use this command, you have to manually subscribe the registeredserver to the correct channels and manually add it to any system groups.

5. Disable access to the Spacewalk Client repository.

Disable Spacewalk Client repository in the Oracle public yum repository configuration file, or deleteyour Spacewalk Client .repo file.

1.5 Known Issues1.5.1 Spacewalk Fails to Install Due to slf4j Package

In some circumstances, the Spacewalk installation can fail if the slf4j (Simple Logging Facade for Java)package is installed. The workaround is to remove the slf4j package. Be aware that Eclipse depends onthis package, so you either have to uninstall Eclipse or remove the package with the rpm -e --nodepsslf4j command.

1.5.2 Tomcat Fails to Start After Spacewalk ConfigurationIf Tomcat fails to start after the initial configuration of Spacewalk, check that the geronimo1.1jtaapipackage is installed. If Oracle Linux is installed using a software set other than Minimal or BasicServer, the jta package might be installed on the system and the presence of this packageprevents the geronimo1.1jtaapi package from being installed. If the geronimo1.1jtaapipackage is missing, you might have to install it manually, after removing the jta package. Thegeronimo1.1jtaapi package is required to ensure that all the Spacewalk services start correctly.

Spacewalk Client Fails to Install on Oracle Linux 5

13

1.5.3 Spacewalk Client Fails to Install on Oracle Linux 5The Spacewalk client conflicts with the up2date client installed by default for connectivity to theUnbreakable Linux Network. Before you install the Spacewalk client for Oracle Linux 5, remove theup2date and up2dategnome packages manually using the rpm -e --nodeps command.

1.5.4 Oracle Linux 5 Does Not Register with Spacewalk after KickstartInstallation

If Oracle Linux 5 does not register with Spacewalk after Kickstart installation, add -up2date and -up2date-gnome to the Kickstart profile on the Software, Package Group screen.

1.5.5 PXE Booting Fails Due to Incorrect Host Name ConfigurationIf the Spacewalk server was installed without a fully-qualified domain name (FQDN), or a name that cannotbe resolved in DNS, Spacewalk creates invalid PXE boot configuration files.

You can validate that Cobbler is configured correctly by checking that the IP address used in the ks=parameter in the /var/lib/tftpboot/pxelinux.cfg/default file is correct.

To reconfigure a Spacewalk server after installation:

1. Edit the /etc/cobbler/settings file and change all instances of incorrect host names, such aslocalhost.localdomain.

2. Restart Spacewalk by running spacewalk-service restart.

3. Resynchronise Cobbler by running cobbler sync.

1.5.6 Out of Memory Issues With Large Repositories or Data SetsWhen building repository metadata, Spacewalk can fail with Out of Memory issues. This is caused by thedefault Java memory settings for the Taskomatic daemon. The solution is to increase the JVM memorysettings in the configuration file for the Taskomatic daemon /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf.

Similar memory issues can also occur in the web interface if you have big data sets, such as a largenumber of servers or packages. The solution is to increase the Tomcat memory limits in the /etc/sysconfig/tomcat6 file. Edit the JAVA_OPTS environment variable, and increase the -Xms (the start orinitial amount of memory) and -Xmx (the maximum amount of memory) parameters.

1.5.7 Client Registration IssuesDuring installation, Spacewalk generates a CA certificate. This certificate is used in the client registrationprocess. If a Spacewalk server does not have a valid fully-qualified domain name (FQDN), Spacewalkdoes not generate a valid CA certificate. Spacewalk does not consider .local and .localdomain to bevalid domain names.

1.5.8 Clients Have to Prerequisite After an UpgradeAfter a Spacewalk server is upgraded, Spacewalk clients might have to re-register with the Spacewalkserver. The web interface shows the clients as registered, but when you run the rhncfg-clientcommand on the client, errors such as Authentication failed: Invalid digital servercertificate are displayed.

Issues With Kickstart After an Upgrade,

14

If this happens, use either the rhn_register or the rhnreg_ks --force command to re-register theclient.

1.5.9 Issues With Kickstart After an Upgrade,After a Spacewalk server is upgraded, using existing kickstart profiles and distributions might result inerrors. The web interface might show error messages such as:

This kickstart profile uses a different type of encryption by default than theroot password is currently using. You must reset the root password to encryptit with the new method.

The solution is:

1. Reset the root password.

2. Restart the Spacewalk service.

# /usr/sbin/spacewalk-service restart

3. Remount your distribution trees and ISO images.

15

Appendix A Legal NoticesThis appendix contains the legal notices that apply to this document.

A.1 Oracle Legal NoticesCopyright 2015, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictionson use and disclosure and are protected by intellectual property laws. Except as expressly permittedin your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by anymeans. Reverse engineering, disassembly, or decompilation of this software, unless required by law forinteroperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing iton behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,any programs installed on the hardware, and/or documentation, delivered to U.S. Government end usersare "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of theprograms, including any operating system, integrated software, any programs installed on the hardware,and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information managementapplications. It is not developed or intended for use in any inherently dangerous applications, includingapplications that may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and othermeasures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damagescaused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarksof their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarksare used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of AdvancedMicro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content,products, and services from third parties. Oracle Corporation and its affiliates are not responsible for andexpressly disclaim all warranties of any kind with respect to third-party content, products, and servicesunless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and itsaffiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use ofthird-party content, products, or services, except as set forth in an applicable agreement between you andOracle.

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program websiteat

DocBook XSL License

16

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers that have purchased support have access to electronic support through My OracleSupport. For information, visithttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

A.2 DocBook XSL LicenseCopyright 1999-2007 Norman Walsh

Copyright 2003 Jiri Kosek

Copyright 2004-2007 Steve Ball

Copyright 2005-2008 The DocBook ProjectCopyright 2011-2012 O'Reilly Media

Permission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the ``Software''), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copiesof the Software, and to permit persons to whom the Software is furnished to do so, subject to the followingconditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portionsof the Software.

Except as contained in this notice, the names of individuals credited with contribution to this software shallnot be used in advertising or otherwise to promote the sale, use or other dealings in this Software withoutprior written authorization from the individuals in question.

Any stylesheet derived from this Software that is publicly distributed will be identified with a different nameand the version strings in any derived Software will be changed so that no possibility of confusion betweenthe derived package and this Software will exist.

Warranty

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESSFOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL NORMAN WALSHOR ANY OTHER CONTRIBUTOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR INCONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Web-based Help from DocBook XMLCopyright 2008-2012 Kasun Gajasinghe, David CramerPermission is hereby granted, free of charge, to any person obtaining a copy of this software andassociated documentation files (the Software), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copiesof the Software, and to permit persons to whom the Software is furnished to do so, subject to the followingconditions:

Web-based Help from DocBook XML

17

The above copyright notice and this permission notice shall be included in all copies or substantialportions of the Software.

Except as contained in this notice, the names of individuals credited with contribution to this softwareshall not be used in advertising or otherwise to promote the sale, use or other dealings in this Softwarewithout prior written authorization from the individuals in question.

Any stylesheet derived from this Software that is publicly distributed will be identified with a differentname and the version strings in any derived Software will be changed so that no possibility of confusionbetween the derived package and this Software will exist.

Warranty: THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESSOR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL DAVIDCRAMER, KASUN GAJASINGHE, OR ANY OTHER CONTRIBUTOR BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHERDEALINGS IN THE SOFTWARE.

Certain search characteristics associated with the DocBook XSL webhelp stylesheets are provided asjavascript files generated using Apache Lucene and other fourth party technologies.

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).


18

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and


19

attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.


20

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Spacewalk 2.2 for Oracle Linux 6Table of ContentsPrefaceChapter1Release Notes1.1About Spacewalk 2.2 for Oracle Linux 61.2Installing and Upgrading Spacewalk1.2.1Oracle Linux Requirements1.2.2Database Requirements1.2.3Storage Requirements1.2.4Network Requirements1.2.5Installing Spacewalk1.2.6Upgrading Spacewalk to Release 2.2

1.3Configuring Spacewalk1.3.1Configuring Software Channels Using ULN1.3.2Configuring Software Channels Using Public Yum1.3.3Synchronizing Software Channels1.3.4Creating Activation Keys for Spacewalk Clients

1.4Installing the Spacewalk Client and Registering Servers1.5Known Issues1.5.1Spacewalk Fails to Install Due to slf4j Package1.5.2Tomcat Fails to Start After Spacewalk Configuration1.5.3Spacewalk Client Fails to Install on Oracle Linux 51.5.4Oracle Linux 5 Does Not Register with Spacewalk after Kickstart Installation1.5.5PXE Booting Fails Due to Incorrect Host Name Configuration1.5.6Out of Memory Issues With Large Repositories or Data Sets1.5.7Client Registration Issues1.5.8Clients Have to Prerequisite After an Upgrade1.5.9Issues With Kickstart After an Upgrade,

AppendixALegal NoticesA.1Oracle Legal NoticesA.2DocBook XSL License

Documents

space walk