Release notes for SUSE Manager Server 2.1

Version 2.1.0
Monday May 11, 2015



This SUSE product includes materials licensed to SUSE under the GNU General Public License (GPL). The GPL requires that SUSE makes available certain source code that corresponds to the GPL-licensed material. The source code is available for download at http://www.suse.com/download-linux/source-code.html.

Also, for up to three years from SUSE's distribution of the SUSE product, upon request SUSE will mail a copy of the source code. Requests should be sent by e-mail to sle_source_request@suse.com or as otherwise instructed at http://www.suse.com/download-linux/source-code.html. SUSE may charge a fee to recover its reasonable costs of distribution.

Version Revision History

Stay up-to-date

You can stay up-to-date regarding information about SUSE Manager and SUSE products:

Major changes since SUSE Manager Server 2.1 GA

Features

Update of certificate

If your SUSE Manager Server 2.1 was a fresh install, you can safely skip this section.

If your SUSE Manager Server 2.1 was upgraded from a previous SUSE Manager Server 1.7 installation, please read on.

The base ('spacewalk') certificate stored in the SUSE Manager database will expire on 2015-July-31st.

To ensure uninterrupted service beyond this date, you need to extend the certificate's expiration date.

To update your spacewalk entitlement certificate please complete the following procedure:

At the server command line run: /usr/lib/susemanager/bin/susemanager-update-swcert.sh

which produces one of the following messages

The update will fail if you have more than one organization setup and are sharing your entitlements across a second or third organization.

The number of entitlements per row on the organization entitlements page cannot exceed 19,999 within a secondary organization. This bug occurs due to an incompatibility with SUSE subscription counting and the old spacewalk certificate.

As a work around log-in to the SUSE Manager web administration page and complete the following procedure.

##### Update successfully finished.#####

You may now re-allocate your original required entitlements on your web admin entitlements page

Expanded support for RHEL7

SUSE Linux Enterprise Server with Expanded Support for RHEL7 is now available in SUSE Manager

Service pack migration via API

Two new API calls now allow to schedule service pack migrations or distribution upgrades via the SUSE Manager API.

system.scheduleSPMigration system.scheduleDistUpgrade

Navigate to Help -> API -> system -> scheduleSPMigration (resp. Help -> API -> system -> scheduleDistUpgrade) for details about these calls.

spacecmd made available to clients

The spacecmd package is now available to managed clients (except for Expanded support for RHEL 5) via the SUSE Manager Tools channel.

Patch filtering in system set manager

When applying patches to an individual system there is a drop down box to show all Security (or Bug Fixes, or Enhancement) patches. This drop down box is now also available for systems in the system set manager.

spacewalk-debug reduced output

spacewalk-debug removes old backup files now before creating the output tar file. This significantly reduces the size of the output file.

Service pack migration with Inter-Server-Sync

Service pack migration for clients attached to Inter-Server-Sync (ISS) slaves is only possible if all parent channels are synced.

The ISS slave needs this information to verify the correctness of base and child channels.

An alternative is to use the `system.scheduleSPMigration`` which does not run these checks.

Support of Inter-Server-Sync with SUSE Customer Center

The switch from Novell Customer Center (NCC) to SUSE Customer Center (SCC) as described below, also effects Inter-Server-Sync (ISS) slaves as follows:

SUSE Customer Center integration

With the release of SUSE Linux Enterprise (SLE) 12, a new online service is available to manage subscriptions, channels, and access to patches.

This is called SUSE Customer Center - SCC

In order to manage SUSE Linux Enterprise Server (SLES) 12 or Desktop (SLED) 12 systems with SUSE Manager, you need to connect SUSE Manager to the SUSE Customer Center.

If you haven't deployed SLE 12, there is no need to connect to SCC.

You will still be reminded in the setup wizard to switch to the SUSE Customer Center. The migration process can be started from the Web UI and will take a couple of minutes.

Please follow these detailed instructions to connect SUSE Manager Server to the SUSE Customer Center.

Be patient, synching the complete data set from SUSE Customer Center can take up to several minutes. This will be improved in later releases.

Changed setup workflow

The initial, text-based setup workflow has been adapted to connect to SCC instead of NCC for the product and subscription data.

New mgr-sync tool

After SUSE Manager Server has been migrated to the SUSE Customer Center, a new tool to manage the data synchronization between both systems will be available.

mgr-sync is a full replacement of mgr-ncc-sync

mgr-sync has a simpler syntax and is easier to use. Run mgr-sync -h for help.

Support for SUSE Linux Enterprise Server and Desktop 12

A SUSE Manager Server connected to the SUSE Customer Center is able to deploy and manage SUSE Linux Enterprise Server and Desktop 12 systems.

Management of PowerPC (ppc64le) systems running SUSE Linux Enterprise Server 12 hasn't seen much testing yet and might be a bit unstable.

Notes

Patches

The SUSE Patch Finder is a simple online service to view released patches.

Patch 10579: SUSE Manager Server 2.1

This collective update for SUSE Manager Server 2.1 provides the following fixes

osad
spacewalk-backend
spacewalk-branding
spacewalk-config
spacewalk-java
spacewalksd
spacewalk-setup
spacewalk-utils
supportutils-plugin-susemanager-client
susemanager-jsp_en and susemanager-manuals_en
susemanager-schema
susemanager
susemanager-sync-data

Patch 10389: postgresql91

The PostgreSQL database server was updated to 9.1.15, fixing bugs and security issues
For a comprehensive list of fixes, please refer to the following release notes
Security Issues

Patch 10275: oracle-update

oracle-update has been updated to fix one security issue
Security Issues

Patch 10309: SUSE Manager Server 2.1

This collective update for SUSE Manager Server 2.1 provides the following new features
Additionally, several issues have been fixed

cobbler
smdba
sm-ncc-sync-data
spacewalk-backend
spacewalk-certs-tools
spacewalk-java
spacewalk-web
supportutils-plugin-susemanager
susemanager-jsp_en, susemanager-manuals_en
susemanager-schema
susemanager
susemanager-sync-data
tanukiwrapper

Patch 10252: spacecmd

This update for spacecmd includes the following fixes

Patch 10076: libyaml-0-2

This libyaml update fixes the following security issue
Security Issues

Patch 10083: SUSE Manager 2.1

This collective update for SUSE Manager Server 2.1 provides the following new features
Additionally, several issues have been fixed

auditlog-keeper
cobbler
osad
pxe-default-image
smdba
sm-ncc-sync-data
spacecmd
spacewalk-backend
spacewalk-branding
spacewalk-certs-tools
spacewalk-java
spacewalk-utils
spacewalk-web
susemanager-manuals_en, susemanager-jsp_en
susemanager-schema
susemanager
susemanager-sync-data

Patch 10022: apache2-mod_wsgi

apache2-mod_wsgi was updated to fix one security issue
Security Issues

Patch 9952: SUSE Manager Server 2.1

This collective update for SUSE Manager Server 2.1 provides the following fixes and enhancements

cobbler
oracle-config
osad
pxe-default-image
smdba
spacecmd
spacewalk-backend
spacewalk-branding
spacewalk-certs-tools
spacewalk-client-tools
spacewalk-config
spacewalk-java
spacewalk-reports
spacewalk-search
spacewalk-setup
spacewalk-utils
spacewalk-web
susemanager-manuals_en, susemanager-jsp_en
susemanager-schema
susemanager
suseRegisterInfo
zypp-plugin-spacewalk
yum

Patch 9812: sm-ncc-sync-data

This update for sm-ncc-sync-data contains the following changes

Patch 9910: spacewalk-java

Security Issues

Patch 9675: perl-Class-Singleton, perl-File-Slurp, perl-JSON, perl-Readonly

Patch 9719: spacewalk-java

Additionally, the following bug was fixed
Security Issues

Patch 9527: oracle-update

Security Issues

Patch 9519: apache2-mod_wsgi

The following issues have been fixed in mod_wsgi
Security Issues

Patch 9430: SUSE Manager Server 2.1

This collective update for SUSE Manager Server 2.1 provides the following fixes and enhancements

auditlog-keeper
osad
rhnlib
rhnpush
spacecmd
spacewalk-backend
spacewalk-branding
spacewalk-java
spacewalk-reports
spacewalk-setup
spacewalk-utils
spacewalk-web
susemanager-schema
susemanager

Patch 9423: struts

Apache Struts was updated to fix a security issue

New features since SUSE Manager Server 1.7

Improved User Interface

The Web UI is now based on the Twitter Bootstrap framework, dramatically enhancing its usability on mobile devices and tablets.

Unattended bare-metal system provisioning

SUSE Manager can be configured so that unprovisioned ("bare-metal") systems capable of PXE booting are added to an organization. After that happens, those systems will appear in the Systems list, where regular provisioning via autoinstallation is possible in a completely unattended fashion.

First-time installation support in System Set Manager

In SUSE Manager 1.7, the System Set Manager Autoinstallation tab could be used to re-install a system using an Autoinstallation profile. With SUSE Manager 2.1, the same tab can be used to create Cobbler system records to install an OS to a machine even if it didn't have one.

This replicates functionality provided by the Create Cobbler System Record button in Manager 1.7 for multiple systems.

Power Management

SUSE Manager allows you to power on, off and reboot systems via the IPMI protocol.

Action chaining

SUSE Manager can group a number of operations in a sequence, called an Action Chain, so that they are all scheduled at once and performed in a particular order.

Using Action Chains can be useful when dealing with some administrative tasks, for example rebooting a systems after deploying a patch. Action chaining can also be controlled via the API. See ‘actionchain’ in the API documentation.

Service location protocol

A SUSE Manager server announces itself via the SLP (service location protocol) service now. This can be used by clients to find the nearest SUSE Manager server to connect to.

Package locks

Locking of packages on the client (via zypper) is now possible. Locking prevents a change in the state of a package. An installed package cannot be upgraded or removed. An uninstalled package cannot be installed.

Setup wizard

This feature moves the CLI-based initial setup of SUSE Manager Server to the web UI. This setup will be started automatically after initial login into SUSE Manager.

The setup workflow will provide proxy settings, mirror credentials, and product selection, including syncing of mandatory channels.

Major changes since SUSE Manager Server 1.7

Base system upgrade to SLES 11 SP3

The underlying SLES 11 base system has been upgraded to Service Pack 3 (including updates)

Upgrade to upstream Spacewalk 2.1

The SUSE Manager code has been updated to reflect the 2.1 release of the upstream Spacewalk project (including updates)

Change in behavior in network setup

The network setup does not default to ‘dhcp’, you need to choose dhcp or static manually.

Non compliant systems

The semantics of ‘non compliant systems’ have been changed. A system is considered ‘non compliant’ if it has packages installed which are not available in a channel. A non compliant system cannot be re-installed.

The old semantics looked for packages in all available channels.

The new semantics look for packages only in channels assigned to the system.

Channel synchronisation logging

Logging of channel synchronisation (triggered by mgr-ncc-sync) was done per channel and sync run. Every new sync created a new log file. A cron job was used to clean up older logs files.

SUSE Manager 2.1 changes this to one log file per channel. All synchronisation runs for a specific channel log to the same file. Older log files are rotated and compressed now using logrotate.

Inter Server Sync between 1.7 (master) and 2.1 (slave)

An inter server sync (ISS) between a SUSE Manager 1.7 Server as master and a SUSE Manager 2.1 Server as client will succeed but generate an error mail to the admin. The error mail is harmless and can be deleted.

Embedded Oracle DB needs extra permission

When upgrading a SUSE Manager Server with Database 1.7 (using embedded Oracle DB), an additional permission (create role) will be added.

New package pgtcl

Stored procedures in PostgreSQL can now be written in the TCL language. The package pgtcl will be added on upgrade.

Reboot action status is reflected immediately in UI

The status of a rebooted client is now updated immediately. There was a delay in the status update in the past.

Taskomatic memory limits lifted

Taskomatic, the scheduler component of SUSE Manager, has an increased memory limitation (raised from 1 GB to 2GB). This might require an increase of main memory.

spacewalk-utils

spacewalk-utils, a packaged set of command line tools, continues to be L1* supported only - with some exceptions. Any of these commands needs expertise and can break your system. However, we consider these tools valuable enough to be included, but not fully supported.

* L1 (Problem determination, which means technical support designed to provide compatibility information, usage support, on-going maintenance, information gathering and basic troubleshooting using available documentation.)

The following tools of spacewalk-utils are fully supported:

SUSE Manager Server requirements

System requirements

SUSE Manager Server is a 64bit Java application with an embedded database backend. This requires sufficient CPU power and main memory. A multi-core 64bit CPU (x86_64) is required, accompanied with a minimum of 4 GB of main memory. Adding more main memory will significantly improve performance.

Disk space requirements

The database will write a recovery log, taking a lot of disk space. You need to follow a strict backup strategy to copy this log to a safe place and reclaim the disk space. See the SUSE Manager manual for details.

Database sizing requirements

The SUSE Manager Server database contains all information required to manage clients. This includes all installable packages and updates as well as lists of installed packages for every client. This data requires a lot of storage space on the harddisk, typically 50 GB or more per package repository.

See the Installation guide for more details on the system requirements.

SUSE Manager Server distribution

SUSE Manager Server is distributed as an appliance which bundles an operating system (SLES 11 SP3 x86_64) with the SUSE Manager Server application and a database. The installable ISO of the SUSE Manager Server appliance can be deployed on physical hardware or fully virtualized (e.g. KVM, VMware) hosts.

Installation and Setup

Installation is done in two major steps. The first installs the appliance and configures the underlying SLES 11 operating system. The second configures SUSE Manager Server and populates the database with initial data. See the Installation guide for step-by-step instructions for installing and configuring SUSE Manager Server. Upgrading from SUSE Manager Server 1.7

An existing SUSE Manager Server 1.7 installation can be upgraded to SUSE Manager Server 2.1 with the help of YaST2 wagon. This is essentially the same workflow as a SLES service pack upgrade.

After the service pack migration has finished successfully, reboot the server and run

  /usr/lib/susemanager/bin/susemanager-upgrade.sh

to complete the SUSE Manager Server upgrade

Be aware that the required database schema migration can be a time-consuming process, esp. if monitoring is enabled and used.

Upgrading from SUSE Manager Server 1.2

An upgrade from SUSE Manager Server 1.2 to SUSE Manager Server 2.1 is not supported. If you still have SUSE Manager Server 1.2 running, please upgrade to SUSE Manager Server 1.7 first and then do the upgrade to SUSE Manager Server 2.1

Migrating from RHN Satellite

It is also possible to migrate data from an existing Red Hat Satellite Server.

Satellite migration requires SUSE Manager Server with an external Oracle database.

The migration itself is a time-consuming process and requires careful planning and expertise. Migration needs to sync the complete database as well as all cached RPM packages. Depending on the network bandwidth and the database setup, this can take up to a day or more.

Depending on the actual database structure and contents, a server migration might also fail. Please report problems via your support channel.

How to apply patches on first install

On first install (i.e. before running yast2 susemanager_setup) just follow the Quick Start guide and apply available patches using either zypper patch or YaST Online Update.

How to apply patches to a running SUSE Manager Server

In general, follow the patch description when installing updates. Only apply updates to a stopped SUSE Manager Server (spacewalk-service stop)

For changes to the database schema, running spacewalk-schema-upgrade is required. Proceed as follows:

  1. Log in as root user to the SUSE Manager server console.
  2. Stop the Spacewalk service: spacewalk-service stop
  3. Apply the patch using either zypper patch or YaST Online Update.
  4. Upgrade the database schema with: spacewalk-schema-upgrade
  5. Start the Spacewalk service: spacewalk-service start

Upgrade from SUSE Manager Server 1.7

SUSE Manager Server 1.7 can be upgraded to SUSE Manager Server 2.1 by the help of YaST wagon, similar to a SLES 11 SP2 to SP3 service pack migration.

Upgrade of Inter Server Sync setups

In ISS (Inter Server Sync) setups, upgrade all slaves to 2.1 before upgrading the master.

Activation of SUSE Manager Server

With the purchase of SUSE Manager Server you will get an activation code. This code needs to be entered at the registration step during installation.

This code enables your SUSE Manager Server to retrieve updates from the Novell Customer Center. Regularly installing updates is a mandatory step to keep your SUSE Manager Server stable and secure. Before applying some updates the SUSE Manager services needs to be stopped and only restarted after the update has been applied. See the SUSE Manager Installation Guide for details.

Entitlement counting in SUSE Manager

SUSE Manager currently doesn't technically limit the number of deployed servers in most cases, except for a theoretical limit of 200,000 entitlements/subscriptions. Please note that this is a technical limitation and does not indicate in any way that you can deploy more servers than you have valid subscriptions for! Later releases of SUSE Manager Server will keep track of allowed and used entitlements for managed systems.

Supportability of embedded software components

All software components embedded into SUSE Manager, like Cobbler for PXE booting, are only supported in the context of SUSE Manager. Stand-alone usage is not supported.

About SLES 12

SUSE Linux Enterprise Server 12 (SLES 12), scheduled for autumn 2014, has a new signing key for packages and repositories. If you upgraded from SUSE Manager 1.7, you need to manually accept this new key into SUSE Manager 2.1 when prompted to.

A fresh installation of SUSE Manager 2.1 will have this key included.

About the Client Tools Channel

The Client Tools Channel contains client-side packages to enable specific functionality. Please refer to the Client Configuration Guide about which packages relate to which function. Some packages have a very specific use case and installing them blindly is discouraged.

Red Hat Channels

Managing Red Hat clients requires availability of appropriate Red Hat packages. These are not available through the Novell Customer Center (NCC) but must be provided by other means, e.g. from a retired Red Hat Satellite installation.

Support for SLES 10 based systems

The SUSE Manager client stack for SLES10 based systems is identical to the one used on SLES11 based systems. SLES 10 systems managed by SUSE Manager will have the ZENworks Managemen Daemon (ZMD) and the rug command line tool removed.

SUSE Manager Proxy versions

SUSE Manager Server 2.1 can work with version 1.7 of SUSE Manager Proxy.

Upgrade of SUSE Manager Proxy from version 1.7 to 2.1 is possible.

Known bugs

Upstream changes since SUSE Manager 1.7

Providing feedback to our products

In case of encountering a bug please report it through your support contact.

Documentation and other information

http://www.suse.com/products/suse-manager/technical-information/contains additional or updated documentation for SUSE Manager Server 2.1.

These Release Notes are available online at http://www.suse.com/documentation/releasenotes. Further information about SUSE Manager is available at http://wiki.novell.com/index.php/SUSE_Manager

Visit http://www.suse.com for the latest Linux product news from SUSE and http://www.suse.com/download-linux/source-code.html for additional information on the source code of SUSE Linux Enterprise products.

Legal Notices

  SUSE Linux GmbH 
  Maxfeldstr. 5 
  D-90409 Nürnberg 
  Tel: +49 (0)911 740 53 - 0 
  Email: feedback@suse.com 
  Registrierung/Registration Number: HRB 21284 AG Nürnberg 
  Geschäftsführer/Managing Director: Jeff Hawn, Jennifer Guild, Felix Imendörffer 
  Steuernummer/Sales Tax ID: DE 192 167 791 
  Erfüllungsort/Legal Venue: Nürnberg

SUSE makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.

Further, SUSE makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses. Please refer to http://www.novell.com/company/policies/trade_services/ for more information on exporting SUSE software. SUSE assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2012 SUSE. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

SUSE has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent applications in the U.S. and other countries.

For SUSE trademarks, see SUSE Trademark and Service Mark list (http://www.novell.com/company/legal/trademarks/tmlist.html). All third-party trademarks are the property of their respective owners.

Colophon

Thank you for using SUSE Manager Server in your business.

Your SUSE Manager Server Team.