Release Notes
3. Type the command, #systemctl restart gdm.service to restart the GDM service.
The user is logged off after running the command.
Issue
VRTX M520 is displayed as M520 in SUU Comparison report.
Issue
VRTX M620 is displayed as M620 in SUU Comparison report.
Issue
Hard drive update is not supported in HBA mode.
Issue
When updating multiple, identical devices on the same system, SUU applies the latest update to all instances of all devices. For
example, if the system is configured with three controllers that are configured with firmware or driver versions 1.2, 1.3, and 1.4,
and the repository version is 1.4, SUU applies version 1.4 to all instances of all devices.(136620)
Issue
When you run SUU using the "-p" option, SUU reports the current instance log location ("suu -p") instead of the SUU instance
log location ("suu -u") that is performing the update.(135925)
Issue
SUU uses DUPs to update various system components. During a Red Hat Enterprise Linux update, the DUPs create a /var/
lock/.spsetup file using the Linux lockfile utility during the initial execution procedure. Kernel panics or sudden reboots
during DUP execution (reboots where TERM signals are not sent to running processes or where running processes do not track
these signals) can generate a /var/lock/.spsetup lock file that cannot be deleted. SUU reports the update as successful
and prompts to reboot the system. When you run SUU again on the same system, the comparison report displays no change in
device status. If this situation occurs and no update is in progress, remove /var/lock/.spsetup before running another
update on the system. (137287)
Issue
If a NIC teaming application is installed on the system, SUU updates only the NIC base driver, if the driver is compatible with the
teaming application. To verify driver compatibility, run DUP on the system to update the driver and read the generated
messages.(138648)
Issue
Devices that are disabled in the operating system are not inventoried or updated by SUU. To update or inventory these devices,
enable the devices in the operating system and then relaunch SUU. (142111)
Issue
Do not use the RAC/iDRAC virtual media to remotely run SUU on a system. This procedure ends the virtual media connection,
resulting in an unsuccessful SUU update.(144487)
Issue
SUU update is unsuccessful if SUU is run from a pathname that contains special characters such as,,:,/,\,$, and so on. It is
recommended to use a directory name without any special characters for running SUU. For example, when a USB DVD-ROM or
USB disk is attached, to a system running SUSE Linux Enterprise Server operating system, mounts it to a directory name that
contains special characters.
For example, /media/USB:1:2/ (42279)
Issue
In Linux, if there is no space in the var partition or tmp folder, SUU displays the following error message: Not enough space
available in the /var or /tmp folder. Please ensure you have atleast 1.5GB.
Resolution
Ensure that you have sufficient space in the var partition or tmp folder and reboot SUU to start the system inventory.(66118)
Issue
To launch SUU on systems running Linux (x64-bit) from Windows CIFS share, do the following—Mount the extracted SUU x32
ISO CIFS share using -o sce=nounix,noserverino options on SUSE Linux Enterprise Server 10 and 11, and on Red Hat
Enterprise Linux 6.2 and 6.3 operating systems (BITS032613).
5