Release Date: Jan. 30, 2009
|Product Versions||ESX 3.5|
|Virtual Machine Migration or Shutdown Required||No|
|Host Reboot Required||No|
|PRs Fixed||277100, 317076|
|Affected Software||iSCSI software|
Also see KB 1001179.
|Related CVE numbers||None|
Summaries and Symptoms
This patch fixes the following issues:
- Changes to iSCSI LUN path policy were not persistent across reboot. This fix makes sure the multi-path configurations are refreshed after iSCSI volumes are discovered, so changes persist after rebooting the ESX system.
Symptoms seen without this patch: Setting changes to pathing or policy preferences on the iSCSI software initiator return to their defaults after rebooting the ESX host. (Unlike iSCSI hardware initiator and fibre initiator settings, which are saved across reboots.)
Note: If the path policy was manually configured by the user at anytime in the past, the next reboot after the patch is installed will set the path policy to the manually-configured value.
- If you customized the /etc/syslog.conf as described in the Basic System Administration guide, changes to the file were overwritten when you upgraded or patched the ESX system.
The syslog.conf file was backed up only when syslog.conf.orig did not exist. This fix changes the backup file to syslog.conf.orig.<year_month_day_hour> so that the configuration file is always backed up.
None beyond the required patch bundles and reboot information listed in the table, above.
Based on VMware KB 1006655