000037196 - Error: Subprocess failed. Error: RPM failed:      installing package kernel-default-4.4.121-92.98.1.x86_64 needs 15MB on the /boot filesystem when applying RSA Identity Governance & Lifecycle November 2018 Appliance Updater for SUSE 12 SP2

Document created by RSA Customer Support Employee on Feb 18, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037196
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Product/Service Type: November 2018 – Appliance Updater for SUSE 12 SP2
IssueWhen applying the November 2018 – Appliance Updater for SUSE 12 SP2, the following error is observed in rsaimg_updater_SLES12_SP2.log(Appliance Updater log:

Retrieving package samba-winbind-4.4.2-38.20.1.x86_64 (115/115), 657.0 KiB (  1.6 MiB unpacked)
Checking for file conflicts: [........done]
(  1/115) Installing: kernel-default-4.4.121-92.98.1.x86_64 [..error]
Installation of kernel-default-4.4.121-92.98.1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed:     installing package kernel-default-4.4.121-92.98.1.x86_64 needs 15MB on the /boot filesystem

Abort, retry, ignore? [a/r/i] (a): a
Problem occurred during or after installation or removal of packages:
Installation aborted by user
Please see the above error message for a hint.
Problem installing OS patches... leaving RSA IMG software halted without Operating System reboot
Operating System patching process has finished
Operating System Patching Failed ... cancelling further patching

 

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:



$ df –h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                  24G     0   24G   0% /dev
tmpfs                     24G   80K   24G   1% /dev/shm
tmpfs                     24G   75M   24G   1% /run
tmpfs                     24G     0   24G   0% /sys/fs/cgroup
/dev/mapper/system-root  713G  273G  405G  41% /
/dev/sda1                140M   97M   33M  75% /boot
tmpfs                    4.7G   16K  4.7G   1% /run/user/482
tmpfs                    4.7G     0  4.7G   0% /run/user/1005
CauseThe /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.

 


ResolutionIt 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

$ rpm -qa | grep kernel-default


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.



kernel-default-4.4.121-92.85.1.x86_64
kernel-default-4.4.114-92.67.1.x86_64


For example, the output below suggests that the running kernel is the latest:

$ uname –a
Linux ysiam01 4.4.121-92.85-default #1 SMP Tue Jun 19 07:41:16 UTC 2018 (1fb8a51) x86_64 x86_64 x86_64 GNU/Linux



2. Run zypper se -s kernel-default and make sure that 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.



$ zypper se -s kernel-default
Loading repository data...
Reading installed packages...
 
S  | Name           | Type    | Version         | Arch   | Repository
---+----------------+---------+-----------------+--------+------------------
i+ | kernel-default | package | 4.4.121-92.85.1 | x86_64 | (System Packages)
i+ | kernel-default | package | 4.4.114-92.67.1 | x86_64 | (System Packages)
v  | kernel-default | package | 4.4.121-92.98.1 | x86_64 | rsaimg_os_updates

 

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:
 



$ zypper rm kernel-default-4.4.114-92.67.1
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following package is going to be REMOVED:
kernel-default-4.4.114-92.67.11 package to remove.
After the operation, 160.3 MiB will be freed.
Continue? [y/n/...? shows all options] (y): y
(1/1) Removing kernel-default-4.4.114-92.67.1.x86_64 .................................................[done]



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.

In the following example, older kernel 4.4.114-92.67 has been removed by zypper rm command, so it's no longer exist under /boot/ partition.




$ ls -l /boot/*4.4.114-92.67*
ls: cannot access '/boot/*4.4.114-92.67*': No such file or directory

NotesIf you're unsure about the above steps, please contact RSA Customer Support for assistance.

Attachments

    Outcomes