Changes between Version 9 and Version 10 of Obsolete/Doc/OS/Errata
- Timestamp:
- Aug 28, 2009, 10:23:26 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Obsolete/Doc/OS/Errata
v9 v10 66 66 Handling of kernel errata is a bit specific due to some restrictions in the current version of SPMA and because an improper upgrade may lead to a machine not restartable. 67 67 68 The kernel version selection, for the kernel itself and all the kernel modules you may used is based on variable `KERNEL_VERSION_NUM`. This variable is typically defined at the beginning of the node profile as it has to match the OS version used (it can also be defined in the the cluster `site/cluster_info.tpl` if all machines in the clusteruse the same kernel version. The value must be the kernel RPM version.68 The kernel version selection, for the kernel itself and all the kernel modules you may used is using the standard [/wiki/Doc/OS/Customization#SelectingKernelVersion kernel selection] method, based on `OS_KERNEL_VERSION` variable. This variable is typically defined at the beginning of the node profile as it has to match the OS version used (it can also be defined in the the cluster `site/cluster_info.tpl` if all machines in the cluster sharing the same OS version use the same kernel version. The value must be the kernel RPM version. 69 69 70 70 But with the current version of SPMA it is not possible to tell SPMA to never uninstall a kernel, even if it is no longer part of the configuration. As a result if you just replace the kernel, the one actually used will be removed at the same time the new one is installed and in case of a problem you may not be able to reboot. A workaround is to add the following lines at the end of the node profile, before the repository configuration), or in any template as part of the errata configuration if you want to avoid editing a large number of profiles (a good place may be the errata fix template, see above). The lines to add are: