|Applies To||RSA Product Set: Identity Governance & Lifecycle|
RSA Product/Service Type: November 2018 – Appliance Updater for SUSE 12 SP2
|Issue||When applying the November 2018 – Appliance Updater for SUSE 12 SP2, the following error is observed in rsaimg_updater_SLES12_SP2.log(Appliance Updater log:|
When looking at df -h command output, the /boot partition shows that 33M of space is available for the operating system, indicating that it should be sufficient:
|Cause||The /boot partition size does not have enough space available for the operating system. We need to remove older kernels that are no longer used by the operating system.|
|Resolution||It would be safe to move older kernel files under /boot/ partition to some backup place and let the new kernel installation finish successfully. However, you need to perform the following check before doing so:|
1. Run the following command and verify the value for kernel-default produces one value
If you are seeing multiple values such as what is shown here, run uname -a and make sure that the running kernel is the latest, in this case 4.4.121.
For example, the output below suggests that the running kernel is the latest:
2. Run zypper se -s kernel-default and make sure that i flag (the first column in the report) is only set on the latest kernel. Using the output from above, it should be set on 4.4.121 and not on 4.4.114.
If you're seeing the i flag set to multiple kernels, including the latest kernel (in the above example, 4.4.121, as above), there might some packages that depend on it, so it did not get removed during the upgrade to 4.4.121. Please run the following command to remove older kernel, in the above example, 4.4.114-92.67.1, but do not break any dependency if reported by Zypper:
If the above command finishes successfully and without conflicts, check to see if any old kernel(s) remains under /boot/. In the above example, /boot/*4.4.114-92.67*. If they are still there, but Zypper does not know anything about them, you can safely move them to a backup location and proceed with the ApplianceUpdater again.
|Notes||If you're unsure about the above steps, please contact RSA Customer Support for assistance.|