Release notes for SUSE Manager 3.1 Server

Version 3.1.11
Wednesday March 20, 2019

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

About SUSE Manager

You have more than just a few Linux servers to manage, maybe even a mixed environment of RHEL and SLES?

Then SUSE Manager is the answer.

SUSE Manager gives you best-in-class open source infrastructure management with new enhancements focused on improving DevOps efficiency, with both RHEL and SLES support from one unified console, maintained and improved by the guys who wrote the fastest and most advanced Linux update stack on the planet.

SUSE Manager gives you the lowest possible Total Cost of Ownership for your Linux environment, from bare metal provisioning to daily patch management. SUSE Manager is an open source (GPLv2) Linux systems management solution that allows you to:

Stay up-to-date

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

Installation

Requirements

SUSE Manager 3.1 Server is an extension for SLES 12 SP4 for x86-64, Power Systems (ppc64le), or z Systems (s390x).

This means that installation is done in two steps

This addresses the need of enterprise deployments to standardize on the base operating system as well as specific storage setups.

It is strongly recommended to use SUSE Manager with the embedded database. PostgreSQL is only supported as a local (embedded) database.

Registration code

The SUSE Manager 3.1 Server registration code, matching your hardware architecture, can be used to register the SLES 12 SP4 base system as well.

Installing the SUSE Manager 3.1 Server extension on SLES 12 SP4

You'll need a physical or virtual SLES 12 SP4 x86_64, ppc64le, or s390x system to install SUSE Manager 3.1 Server.

When you install and register SLES 12 SP4, SUSE Manager 3.1 Server will show up in the list of available extensions.

You'll need a valid SUSE Manager 3.1 Server registration code to access this extension.

Update from previous versions of SUSE Manager Server

You can update from SUSE Manager 3.0 Server to SUSE Manager 3.1 Server.

Updates from older versions are not possible.

Note that SUSE Manager 3.0 has already reached end-of-life (EOL) and is not fully supported anymore. It is strongly advised to have an experienced SUSE sales engineer, SUSE consultant, or SUSE partner help with this migration.

The actual upgrade can be done in two steps:

1. Migrate SUSE Manager 3.0 Server to 3.1, both based on SLES 12 SP3.

2. Migrate SUSE Manager 3.1 from SLES 12 SP3 to SLES 12 SP4.

Your SUSE Manager Server 3.0 must be up-to-date (Version 3.0.12 as of this writing) before you can attempt to upgrade to SUSE Manager Server 3.1.

Make sure that your SUSE Manager Server 3.0

See the Version 3.1.2 paragraph below and consult the best practices manual for detailed instructions on how to upgrade.

All connected clients will continue to run and are manageable unchanged.

Migrating from RHN Satellite

Is conditionally supported with SUSE Manager 3.1 Server.

If you have the need to migrate from RHN Satellite to SUSE Manager 3.1 Server, please get in contact with a SUSE sales engineer or a SUSE consultant before starting the migration.

Scaling SUSE Manager

The default configuration of SUSE Manager, when deployed on appropriate hardware as described in the getting started guide, will scale to a 4-digit number of clients.

Scaling beyond that number needs special consideration as described in the advanced topic guide

One size never fits all. Getting advise from a SUSE partner, sales engineer, or consultant is recommended to adapt SUSE Manager to your environment.

Channels with large number of packages

Some channels, like SUSE Linux Enterprise Server with Expanded Support or Redhat Enterprise Linux, come with an enormous number of packages.

If you have channels with a large number of packages added to SUSE Manager, taskomatic might run out of memory.

In this case it's recommended to increase the maximum amount of memory allowed for taskomatic by editing /etc/rhn/rhn.conf and adding 

      taskomatic.java.maxmemory=4096

to this file.

A restart of taskomatic is needed after this change.

The number 4096 gives 4 GB of memory to taskomatic (up from the default 2GB) and should be raised even higher if taskomatic still runs out of memory.

Keep in mind this will affect to the total memory required by SUSE Manager Server.

Major changes since SUSE Manager Server 3.1 GA

Features and changes

Version 3.1.11

New products supported

Version 3.1.10

New API calls

Functions softwarechannel_mergepackages and softwarechannel_errata_merge to merge packages and errata through spacecmd were added.

New products supported

Version 3.1.9

PostgreSQL 10 support

A new version of the PostgreSQL database is available in SLES 12 SP3 and SP4 and can be used for SUSE Manager 3.1 Server.

New installations of SUSE Manager 3.1 Server based on SLES 12 SP4 will automatically pick up this version.

PostgreSQL 10 needs a new version of smdba to initiate backups. This version is part of the SUSE Manager 3.1.9 patch.

Migrating from PostgreSQL 9.6 to PostgreSQL 10

You should have an up-to-date database backup before attempting the migration.

Recommendation: Migrate from PostgreSQL 9.6 to 10 first, then SLES 12 SP3 to SLES 12 SP4.

Existing installations of SUSE Manager 3.1 Server will need to run 

      /usr/lib/susemanager/bin/pg-migrate-96-to-10.sh

to migrate from PostgreSQL 9.6 to PostgreSQL 10

Your SUSE Manager Server installation will not be accessible during the migration.

Note The migration will create a copy of the database under /var/lib/pgsql and thus needs sufficient disk space to hold two copies (9.6 and 10) of the database.

Since it does a full copy of the database, it also needs considerable time depending on the size of the database and the IO speed of the storage.

If your system is scarce on disk space you can do an fast, in-place migration by running 

      /usr/lib/susemanager/bin/pg-migrate-96-to-10.sh fast

The fast migration usually only takes minutes and no additional disk space. However, in case of failure you need to restore the database from a backup.

This wiki page contains additional information about the database migration.

SUSE Manager Server enabled for SLES 12 SP4

SUSE Manager 3.1 is now based on SLES 12 SP4. You can switch as soon as SLES 12 SP4 is available.

If you already have a SUSE Manager 3.1 Server or Proxy deployed, you can now initiate a service pack migration as outlined in the SLES documentation

Recommendation: Migrate from PostgreSQL 9.6 to 10 first, then SLES 12 SP3 to SLES 12 SP4.

If you deploy a SUSE Manager 3.1 Server or Proxy anew, please start with SLES 12 SP4 as the base operating system.

In case you plan to upgrade to SUSE Manager 3.2 soon, wait for the SLES 12 SP4 enablement in SUSE Manager 3.2. This will come with the 3.2.4 release soon.

spacecmd: Support state channels

spacecmd, the command line access to the SUSE Manager API, has been adapted to support state channels (aka Salt Minion config channels) with the following changes

Please use the help functionality of spacecmd for detailed option descriptions for each mentioned call.

Version 3.1.8

Bugfix release.

Check for Dynamic CA-Trust Updates while bootstrapping on RES

When bootstrapping an ES6.x system the SUSE Manager CA certificate will be imported by the client.

When dynamic CA-Trust Updates are disabled ( as per default ), the registration and bootstrapping of the client will fail, giving a lot of output and making it difficult to find the real cause.

This update adds a short check at the start of the bootstrap script to advise the sysadmin to enable ca trust updates.

Dot character forbidden in configuration channel label

The dot character (.) is now forbidden in configuration channel label, as it does not work with salt clients.

A . character in existing configuration channels needs to be manually replaced by another character, e.g. _.

Version 3.1.7

Bugfix release.

Version 3.1.6

Bugfix release.

Update to Salt 'Oxygen' 2018.3.0

Salt is updated to the 'Oxygen' release, versioned as 2018.3.0.

This brings many changes and improvements all over the place, most notably in Python 3 support, Unicode, and Docker.

See the Salt Oxygen and Salt Nitrogen release notes for a full description of changes since SUSE Manager's previous Salt version.

Support of SLE 15 products

This update adds support for SLE 15 products and

Salt on SLE 11 and RHEL 5

Salt deprecated Python 2.6 with the release of Salt Nitrogen in 2017.

Client systems with Python 2.6, like SLE 11 or RHEL 5, will therefore NOT get Salt upgrades and stay with their current Salt version.

Python 3 subpackages

In order to support SLE 15 clients with salt-ssh, Python 3 compatibility packages are added in this update.

This enables salt-ssh to use Python 3 code when running on SLE 15 clients, which have Python 3 as their main Python version.

spacecmd updates

spacecmd now has a new command: softwarechannel_update (Update a software channel) The spacecmd functions softwarechannel_create, softwarechannel_clone, and softwarechannel_tree now have a new parameter -g DISABLE-GPG-CHECK.

See 'spacecmd reference' in the advanced topics manual for details.

New products supported

Version 3.1.5

Package timestamp problem fixed

Due to different package timestamps in the database and repository metadata, zypper cannot correctly match installed to available packages.

This is a generic problem since version 3.1.0 and cannot be fixed with a simple update.

Version 3.1.5 will only fix the code to import the package timestamp into the database, it will not fix the existing timestamps in the database.

To address this, please run

/usr/sbin/align-rpm-buildtime

to fix the existing timestamps in the database.

Note(1): The script took around 43 minutes to complete on a production system, correcting nearly 60000 package entries in the database. Once the script finished, it triggers a recreation of the repository metadata at /var/cache/rhn/repodata. Please wait for this process to finish as well before checking if the issue has been resolved.

Note(2): On systems with low memory configuration (e.g. test environments, 8GB RAM / 4GB assigned to taskomatic) the script may stop with the message "killed". This happens due to insufficient system memory needed by postgress for this operation. In this case please add more RAM to the system.

See also TID#7022656

API: Channel change is now an action

The 'channel change on minions' introduced in version 3.1.2 is now correctly reflected in th API.

Until now the API calls (system.setBaseChannels(), system.setChildChannels()) applied the changes immediately and returned 1 (OK) or an exception.

Now both API calls are deprecated and system.scheduleChangeChannels() takes care of it as an action that is scheduled.

New API call
Deprecated API calls

New products supported

Version 3.1.4

Configuration Management for Salt is not tech preview anymore

With this version, configuration management for Salt goes out of 'tech preview' and becomes a fully supported feature.

Changes in "Custom States" and "State Catalog" features

The salt custom state management has been reworked and now it is a part of the "Configuration" feature.

Salt "Custom States" have been replaced with "State Channels". A "State Channel" is a special type of a "Configuration channel" which includes an editable init.sls file.

Previously, the "State Catalog" was used for listing and manipulating the "Custom States". From now on, this is done via the "Configuration -> Configuration Channels" in the web UI.

Migration

During the database migration, for every "Custom State" there is a new "State Channel" created and its assignment to servers / server groups / organizations is updated based on the original assignment of the "Custom State".

Previously, the content of the "Custom State" was only stored in the filesystem. With the "State Channels", the state content is part of a configuration file in the database. The database entries of the files need to be populated and this happens as a part of a one-time migration function on the tomcat startup.

Support Proxies with multiple FQDNs

SUSE Manager Proxy, when also used to separate network segments, requires two network interfaces. One server-facing interface and one client(s)-facing interface.

Having both interfaces different network domains was not supported in the past, since the proxy's DNS name as used by the client(s) and the proxy's DNS name as used by the server had to match.

Now the proxy's DNS names on both interfaces can be different and the server will detect that both are pointing to the same SUSE Manager Proxy.

Excessive logging reduced

The salt-daemon-watcher cron entry has been changed to reduce logging to syslog.

New notification UI

A new UI component to display notifications has been added.

The aim of a notification message is to inform the user about some event that just happened on the SUSE Manager Server.

To deliver this information in real-time a new UI component has been added, fixed in the header of each page: a bell icon with a counter bubble of how many unread notification messages the user has.

Notification messages are listed in a new page at "Home > Notification Messages".

Initially, this will show three type of messages:

Each message can be flagged as 'read' or 'unread' or deleted completely. For each failure a customized button (in line with the message) is available to react to that failure.

The set of type of messages will be extended to cover more information in later releases.

New API calls

Version 3.1.3

Database cleanup migration

After several reports about duplicate package ids in the database, a cleanup task was introduced in spacewalk-schema-upgrade to repair such cases.

Warning In case your database is corrupted with duplicate package ids, this cleanup task can take hours to complete. Runtimes of 4-5 hours are normal.

Here is how to check for duplicate package ids 

  echo "select min(id) as id \
         from rhnpackageevr \
        group by version, release, epoch \
          having count(*) > 1;" \
    | spacewalk-sql --select-mode-direct -

  echo "select min(id) as id \
          from rhnPackageCapability \
          group by name, version \
          having count(*) > 1;"\
    | spacewalk-sql --select-mode-direct -

These read-only checks can be run during normal operation of SUSE Manager. Just running the checks can take a long time (up to 1hr in some of our test scenarios. YMMV).

If any of these queries returns a non-empty result, it can be stopped immediately. Your database has duplicate package ids in this case and the next run of spacewalk-schema-upgrade will take hours.

Take this under consideration before starting the upgrade to SUSE Manager 3.1.3.

Check for duplicate minion ids

With this update we introduce a unique constraint on minion_id in the database.

When multiple systems exists already with the same minion_id, the schema migration will fail.

There will be a list of the duplicates in the schema migration log. In this case, duplicate minion_id need a manual cleanup:

Minion configuration channels

Configuration channels, allowing central deployment of configuration files to clients, are now available for Salt minions.

This feature is a tech-preview and will be enhanced in future releases of SUSE Manager 3.1.

See 'Configuration Management for Salt ' in the Reference manual for the currently enabled functionality and its limitations.

Minion power management

Power management (power on, off, and reboot systems via the IPMI protocol if the systems are IPMI-enabled) is now enabled for Salt minions.

PostgreSQL backup configuration

During the migration of PostgreSQL from 9.4 to 9.6, the backup configuration might get lost and needs to be recreated with smdba.

Documentation

The 'image building' chapter was improved and moved to the Advanced Topics manual.

Removal of Certification Module for SLES 12 SP2 and SP3

Certification Module was accidently provided for SLES12 SP2 and SP3.

But this module does not exist for these service packs and got removed in SUSE Manager.

If you have mirrored this module for SP2 or SP3, please remove the channels using spacewalk-remove-channel command

New products supported

Version 3.1.2

PostgreSQL 9.6 support

A new version of the PostgreSQL database is available in SLES 12 SP2 and can be used for SUSE Manager 3.1 Server.

New installations of SUSE Manager 3.1 Server based on SLES 12 SP3 will automatically pick up this version.

Migrating from PostgreSQL 9.4 to PostgreSQL 9.6

Note: SUSE Manager 3.1 Server must NOT be migrated to SLES 12 SP3 before migrating PostgreSQL to version 9.6.

The migration needs PostgreSQL 9.4 and 9.6 installed in parallel and PostgreSQL 9.4 is only available in SLES 12 SP2

You should have an up-to-date database backup before attempting the migration.

Existing installations of SUSE Manager 3.1 Server will need to run 

      /usr/lib/susemanager/bin/pg-migrate.sh

to migrate from PostgreSQL 9.4 to PostgreSQL 9.6

Your SUSE Manager Server installation will not be accessible during the migration.

Migration will create a copy of the database under /var/lib/pgsql and thus needs sufficient disk space to hold two copies (9.4 and 9.6) of the database.

Since it does a full copy of the database, it also needs considerable time depending on the size of the database and the IO speed of the storage.

If your system is scarce on disk space you can do an fast, in-place migration by running 

      /usr/lib/susemanager/bin/pg-migrate.sh fast

The fast migration usually only takes minutes and no additional disk space. However, in case of failure you need to restore the database from a backup.

This wiki page contains additional information about the migration.

SUSE Manager Server enabled for SLES 12 SP3

SUSE Manager 3.1 is now based on SLES 12 SP3.

If you already have a SUSE Manager 3.1 Server or Proxy deployed, you can now initiate a service pack migration as outlined in the SLES documentation.

Please migrate to PostgreSQL 9.6 as outlined above before starting the service pack migration.

If you deploy a SUSE Manager 3.1 Server or Proxy anew, please start with SLES 12 SP3 as the base operating system.

Release notes and documentation have been adapted to reflect this.

Channel changes on minions

This update brings an important change in semantics when changing channel assignments on minions.

In the past, channel assignment changes were executed immediately, without respecting config change time slots. Effectively doing a 'change of client configuration outside of a maintenance window'.

This is fixed with 3.1.2 by delaying state application until

A respective web UI information is also shown for the client.

SUSE CaaS Platform / Kubernetes integration

This update brings the initial integration of SUSE Manager with version 1 of the SUSE CaaS Platform

You can now search containers running on the SUSE CaaS Platform for

The SUSE CaaS Platform / Kubernetes infrastructure data can also be visualized via the Systems > Visualization page.

Container inspection / Image import

Inspection of containers build by SUSE Manager was already part of the 3.1 release.

Now you can also import and inspect any 'foreign' container image available in the configured container registry.

This feature is currently limited to SLES-based containers. The container needs to have Python installed.

Version 3.1.1

Bugfix release

New products supported

Patches

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

Version 3.1.11

cobbler:

py26-compat-salt:

spacecmd:

spacewalk-branding:

spacewalk-java:

spacewalk-utils:

spacewalk-web:

subscription-matcher:

susemanager:

susemanager-schema:

susemanager-docs_en:

susemanager-frontend-libs:

susemanager-sync-data:

tika-core:

Version 3.1.10

cobbler:

spacecmd:

spacewalk-backend:

spacewalk-branding:

spacewalk-certs-tools:

spacewalk-java:

spacewalk-setup:

spacewalk-utils:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-sync-data:

Version 3.1.9

Server

py26-compat-salt:

smdba:

spacecmd:

spacewalk:

spacewalk-backend:

spacewalk-branding:

spacewalk-doc-indexes:

spacewalk-java:

spacewalk-search:

spacewalk-utils:

spacewalk-web:

subscription-matcher:

susemanager:

susemanager-branding-oss:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

Version 3.1.8

Server

cobbler:

py26-compat-salt:

spacecmd:

spacewalk-branding:

spacewalk-certs-tools:

spacewalk-java:

spacewalk-search:

spacewalk-web:

spark:

susemanager-schema:

susemanager-sync-data:

Version 3.1.7

Server

cobbler:

nutch:

spacecmd:

spacewalk-backend:

spacewalk-java:

spacewalk-utils:

spacewalk-web:

susemanager:

susemanager-frontend-libs:

susemanager-schema:

susemanager-sls:

Version 3.1.6

Server

cobbler:

google-gson:

patterns-suse-manager:

release-notes-susemanager:

salt-netapi-client:

spacewalk-backend:

spacewalk-branding:

spacewalk-certs-tools:

spacewalk-java:

spacewalk-utils:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

susemanager-tftpsync:

Salt

salt:

supportutils-plugin-salt:

Client tools

cobbler:

hwdata:

osad:

python-websocket-client:

rhn-custom-info:

rhn-virtualization:

rhncfg:

rhnlib:

rhnpush:

spacecmd:

spacewalk-backend:

spacewalk-client-tools:

spacewalk-koan:

spacewalk-oscap:

spacewalk-remote-utils:

spacewalk-usix:

spacewalksd:

supportutils-plugin-susemanager-client:

suseRegisterInfo:

zypp-plugin-spacewalk:

Version 3.1.5

Server

spacecmd:

spacewalk-backend:

spacewalk-branding:

spacewalk-certs-tools:

spacewalk-client-tools:

spacewalk-java:

spacewalk-reports:

spacewalk-web:

subscription-matcher:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

susemanager-tftpsync:

virtual-host-gatherer:

Client tools

python-docker-py:

spacecmd:

spacewalk-backend:

spacewalk-client-tools:

zypp-plugin-spacewalk:

Salt

salt:

Version 3.1.4

Server

nutch:

osad:

pxe-default-image:

rhnlib:

spacecmd:

spacewalk-backend:

spacewalk-branding:

spacewalk-client-tools:

spacewalk-java:

spacewalk-reports:

spacewalk-search:

spacewalk-utils:

spacewalk-web:

susemanager:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

virtual-host-gatherer:

susemanager-docs_en:

Salt

salt:

Version 3.1.3

Server

cobbler:

nutch:

osad:

spacecmd:

spacewalk-backend:

spacewalk-branding:

spacewalk-certs-tools:

spacewalk-java:

spacewalk-reports:

spacewalk-search:

spacewalk-web:

supportutils-plugin-salt:

supportutils-plugin-susemanager:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

virtual-host-gatherer:

Salt

salt:

Client tools

cobbler:

osad:

spacecmd:

spacewalk-backend:

spacewalk-oscap:

supportutils-plugin-salt:

zypp-plugin-spacewalk:

Version 3.1.2

Client tools

spacecmd:

spacewalk-backend:

supportutils-plugin-salt:

Salt

The following security issue has been fixed:

Additionally, the following non-security issues have been fixed:

Server

salt-netapi-client:

smdba:

spacecmd:

spacewalk:

spacewalk-backend:

spacewalk-branding:

spacewalk-config:

spacewalk-doc-indexes:

spacewalk-java:

spacewalk-web:

supportutils-plugin-salt:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sls:

susemanager-sync-data:

virtual-host-gatherer:

python-websocket-client:

Version 3.1.1

jabberd:

osad:

salt-netapi-client:

smdba:

spacecmd:

spacewalk-backend:

spacewalk-branding:

spacewalk-certs-tools:

spacewalk-java:

spacewalk-search:

spacewalk-utils:

spacewalk-web:

susemanager:

susemanager-docs_en:

susemanager-schema:

susemanager-sync-data:

Major changes since SUSE Manager 3.0 Server

Upgrade of base system to SLES 12 SP2

SUSE Manager 3.1 is based on SLES 12 SP2 as its base operating system.

SUSE Manager Proxy versions

SUSE Manager 3.1 Server can work with version 3.0 of SUSE Manager Proxy.

When upgrading, upgrade the server first, followed by proxies. See the advanced topics manual for detailed upgrade instructions.

Spacewalk 2.6

SUSE Manager 3.1 Server is based on Spacewalk 2.6 with many new features added by SUSE.

Managing Container Images

You can now enable Salt minions to act as container build hosts.

Manage and audit your container images by creating image stores, define image profiles and build images.

For more information see 'Building Containers' in the reference manual.

UI and Usability

Reduced vertical waste

The page header has been improved to dramatically reduce the space wasted, giving more visibility to the actual page content.

New navigation structure

The horizontal navigation items have been moved from the page header to the left navigation plane. See 'Navigation' in the reference manual.

Action buttons visibility

Action buttons, historically placed at the end of lists, have been moved to the top and will stay visible even if the list is scrolled down.

Top of page button

A shortcut to scroll up to the top of the page has been added to the lower right corner of the UI.

Visualization

You can now visualize your systems infrastructure. This feature allows you to search, filter and partition systems by name, base channel, check-in date, etc.

The initial release focusses on data from the SUSE Manager database.

Future improvements will enrich this with data from external systems, like monitoring systems or virtualization hosts.

Scalability

SUSE Manager 3.1 Server provides many scalability enhancements over SUSE Manager 3.0 Server. Some operations have seen a ten-fold speed improvement over previous releases.

We will continue to invest into this area in further maintenance updates.

Automatic product installation

If a newly added child channel provides a SUSE product (like a SLES module or extension), this product is automatically installed.

Salt

Salt update to 2016.11.4

Salt has been upgraded to the 2016.11.4 release. This represents the 'latest & greatest' release from upstream at time of 'code freeze' for SUSE Manager 3.1.

We do intend to upgrade Salt regularly to more recent versions.

Minions in the system set manager

The system set manager (SSM) now supports minions. You can as well add or remove a minion from the current set.

The System Set Manager Overview page has an 'Apply Highstate' button now.

Bootstrap defaults to SALT now

The 'bootstrap' script by default installs a Salt minion now.

The --salt option is deprecated.

Use --traditional to install a traditional (non-Salt) client.

OpenSCAP for minions

You can now work with OpenSCAP and Salt minions. To begin using OpenSCAP with Salt minions you can follow the traditional setup guide

This feature does not yet work for minions attached via salt-ssh.

Change of jabberd database

jabberd now uses sqlite in place of the berkeley db database to improve stability and performance. sqlite is the preferred database option for jabberd.

Fresh installations of SUSE Manager 3.1 Server will use sqlite by default.

Existing installation need to manually switch to this database as follows 

      # systemctl stop jabberd
      # spacewalk-setup-jabberd
      # systemctl start jabberd

jabberd removal and recreation

Notice that the sqlite variant of the jabberd database does not get re-created automatically.

The workaround for corruptions of the old database - regular removal - does not apply anymore.

In case you erroneously deleted the sqlite database, jabberd will not be able to re-create it.

You need to run /usr/share/spacewalk/setup/jabberd/create_sqlite3_database to create the database schema and restart jabberd.

Formulas with Forms

Salt formulas can be integrated with the Manager UI. A sample Formula with Form to configure locale-related settings (timezone/locale/keyboard) is included.

Upstream changes since SUSE Manager 3.0

Note: Changes from the upstream project are listed here as-is. There's no guarantee that all of them are actually available in SUSE Manager 3.1 Server.

Spacewalk 2.6

Spacewalk 2.5

Support

Supportconfig confidentiality disclaimer

When handling Service Requests, supporters and engineers may ask for the output of the supportconfig tool from the SUSE Manager Server or clients.

The standard disclaimer applies: 

  Detailed system information and logs are collected and organized in a
  manner that helps reduce service request resolution times.
  Private system information can be disclosed when using this tool.
  
  If this is a concern, please prune private data from the log files.
  
  Several startup options are available to exclude more sensitive
  information. Supportconfig data is used only for diagnostic purposes
  and is considered confidential information.

In the SUSE Manager Server's case, please be aware that supportconfig's output will contain information about clients as well.

In particular, debug data for the Subscription Matching feature contain a list of the registered clients, their installed product and some minimal hardware information (CPU socket count). It also contains a copy of subscription data available from the SUSE Customer Center.

If this is a concern, please prune data in the subscription-matcher directory in the spacewalk-debug tarball.

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.

Red Hat Channels

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

Support for EOL'ed products

The SUSE Manager engineering team provides 'best effort' support for products past their end-of-life date. See the Product Support Lifecycle page.

This support is limited to scenarios to bring production systems to a supported state. Either by migrating to a supported service pack or by upgrading to a supported product version.

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.

Salt is not available for SLES 10.

Note that SLES 10 has already reached its end-of-life date and engineering only provides 'best effort' support.

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:

Providing feedback to our products

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

Documentation and other information

Technical Information: SUSE Manager contains additional or updated documentation for SUSE Manager Server 3.1.

These Release Notes are available online. Further information about SUSE Manager is available in the Wiki

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 the Microfocus Legal information page for more information on exporting SUSE software. SUSE assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2017 SUSE LLC. 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. 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.