SUSE-RU-2019:3245-1: moderate: Recommended update for azure-li-services

sle-updates at sle-updates at
Wed Dec 11 07:31:40 MST 2019

   SUSE Recommended Update: Recommended update for azure-li-services

Announcement ID:    SUSE-RU-2019:3245-1
Rating:             moderate
References:         #1157040 #1157041 
Affected Products:
                    SUSE Linux Enterprise Module for Public Cloud 15-SP1
                    SUSE Linux Enterprise Module for Public Cloud 15

   An update that has two recommended fixes can now be


   This update for azure-li-services fixes the following issues:

   - Bump version: 1.2.3 to 1.2.4

   - Reference commit for SUSE maintenance This submission creates a
     reference to bsc#1157041

   - Reference commit for SUSE maintenance This submission creates a
     reference to bsc#1157040

   - Bump version: 1.2.2 to 1.2.3

   - Right name for vli sp2 folder

   - Add folder for SLES15 SP2 VLI images

   - Fixed VLI package list for sle15 cpp48 does not exist on sle15, instead
     the cpp package by its name provides is used. On sle15 this resolved to
     cpp7. This is related to Issue #186

   - Bump version: 1.2.1 to 1.2.2

   - Added Microsoft requested packages to VLI images This Fixes #186

   - Add retry loop to setup sbd device There is no deterministic way to know
     when the iSCSI device is ready to be processed by sbd. Thus the calls to
     setup the sbd device has been placed into a retry loop that runs max 3
     times with a 2sec wait period in between. This Fixes #188

   - Add directory for SLES15-SP2

   - Saptune setup As pointed before, saptune supersedes sapconf. This is the
     right path to setup saptune. Update image descriptions not to install
     sapconf. This Fixes #185

   - Update LI image versions For the refresh of the images in the SUSE
     namespace the version number has been increased

   - Bump version: 1.2.0 to 1.2.1

   - Right sequence saptune

     One of the issues is that `saptune` is a different tool that supersedes
   `sapconf`. Then the `saptune daemon restart` command will always
     overwrite the profile with `saptune`. Two different tools that can't be
      mixed. Only one should be used. In case of SLES (not SLES for SAP), the
      sequence should be For SLES 12 ``` tuned-adm profile sap-hana systemctl
      enable --now sapconf.service ``` and for SLES15 ``` tuned-adm profile
      sapconf systemctl enable --now sapconf.service ``` For SLES for SAP,
      the sequence is the same for 12 and 15: ``` saptune daemon start
      saptune solution apply HANA ``` This Fixes #172

   - Bump version: 1.1.39 to 1.2.0

   - Change the setup of the login shell The login shell was setup based on
     assumption regarding other user attributes set. This way caused some
     negative side effects which lets us change the behavior. This patch does
     the following
     * Adds a new attribute named: loginshell
     * If loginshell is present the value for loginshell will be used, if not
       the default /sbin/nologin applies
     * All implicit assumptions for setting up the login shell got deleted

       This Fixes #178

   - sbd device to wait for udev to finish This Fixes #179

   - Bump version: 1.1.38 to 1.1.39

   - Consolidate all image descriptions in git Instead of maintaining image
     descriptions in obs we want to maintain them in git. With this change
     only a service and multibuild configuration applies in obs but the data
     to build the image will live in git. This allows for real development
     and review regarding changes to the kiwi image descriptions.

   - Restart iscsi subsystem after device discovery Only after restart of the
     iscsi subsystem the device nodes from a previous device discovery gets
     created properly. This Fixes #170

   - Bump version: 1.1.37 to 1.1.38

   - Added more logging to the process Add a log file
     /var/log/azure-li-services.log which adds logging information from the
     service process. Usually error log information is present on the systemd
     level but for checking the process, it's calls and potential further
     information it's also useful to have a processing log file. The log file
     will be created on the host and gets also copied to the config lun in
     the same way as the systemd workload log

   - Bump version: 1.1.36 to 1.1.37

   - Delete ineffective startup.nsh code startup.nsh is read by the firmware
     in an early boot phase. It doesn't make sense to write that file as part
     of the boot services because it's too late in the process. startup.nsh
     if required needs to be provided by the image itself

   - Extend storage service dependencies The storage service can be used for
     remote storage like NFS storage to be attached to the machine. This
     requires the network to be online. Having the network only configured is
     not enough it must also be online. Thus the storage service unit is
     extended to wait for the

   - Bump version: 1.1.35 to 1.1.36

   - Fixed network setup for bonding on vlan vlan network definitions that
     uses bonding etherdevices were missing a switch to correctly assign the
     ip configuration This Fixes #164

   - Bump version: 1.1.34 to 1.1.35

   - Apply saptune startup sequence suggested by $MS Implementing startup
     sequence as suggested in SAP Note 1275776. This Fixes #149

   - Log command calls on the console Implements a simple logging facility
     for the Command classes and write the commands called to the console.
     This will lead to more detailed information about the command calls in
     the systemd status information

   - Load yaml in safe mode The default yaml loader is unsafe, thus we should
     switch to the safe_load method. For details see:

   - Bump version: 1.1.33 to 1.1.34

   - Start saptune daemon after applying profile For some reason the saptune
     daemon needs to restart if a profile has been set through the tuned-adm
     profile command. This Fixes #149

   - Revert fix for service order of saptune daemon It has turned out that
     the simple change in order did not solve the problem. In fact the daemon
     needs to be restarted on profile setup

   - Allow ssh access with shell Allow access through ssh without shadow hash
     and with shell. Fixes #151

   - Bump version: 1.1.32 to 1.1.33

   - Fix service order on startup of saptune daemon The tuned profile must be
     applied prior to the start of the saptune daemon. This Fixes #149

   - Bump version: 1.1.31 to 1.1.32

   - Fixed travis badge link

   - Mount LUN in sync mode Per request from Microsoft the location that
     holds the config file and is also used for the status flag and log
     should be mounted with the sync option. This Fixes #144

   - Activate SAP Hana profile via tuned-adm Check for the presence of the
     sap-hana profile and switch to sapconf if not found. Activate the
     selected profile via the tuned-adm control command. This Fixes #142

Patch Instructions:

   To install this SUSE Recommended Update use the SUSE recommended installation methods
   like YaST online_update or "zypper patch".

   Alternatively you can run the command listed for your product:

   - SUSE Linux Enterprise Module for Public Cloud 15-SP1:

      zypper in -t patch SUSE-SLE-Module-Public-Cloud-15-SP1-2019-3245=1

   - SUSE Linux Enterprise Module for Public Cloud 15:

      zypper in -t patch SUSE-SLE-Module-Public-Cloud-15-2019-3245=1

Package List:

   - SUSE Linux Enterprise Module for Public Cloud 15-SP1 (noarch):


   - SUSE Linux Enterprise Module for Public Cloud 15 (noarch):



More information about the sle-updates mailing list