/boot mount space issue which was termed as optional is creating issue

Products

• CA API Gateway

Issue/Introduction

A lower environment has successfully been upgraded to 11.1 version. After starting the upgrade for the production nodes, on the very first node, it seems the platform file 'Layer7_API_PlatformUpdate_v11.1.00-Debian-17707.L7P' installation is failing. Also, it seems it's giving error that /boot does not have sufficient space. 

Running PatchClient with arguments: [upload, /home/ssgconfig/Layer7_API_Gateway_Debian_v11.1.00-17707.L7P]
Nov 05, 2024 7:43:55 AM com.broadcom.patchman.client.PatchClient main
INFO: Running PatchClient with arguments: [install, Layer7_API_Gateway_Debian_v11.1.00-17707]
Nov 05, 2024 7:45:17 AM com.broadcom.patchman.client.PatchClient main
INFO: Running PatchClient with arguments: [list]
Nov 05, 2024 7:47:25 AM com.broadcom.patchman.client.PatchClient main
INFO: Running PatchClient with arguments: [list, -sort, INSTALLED::UPLOADED::ERROR|-LAST_MOD::-LAST_MOD::-LAST_MOD, ::id::description::state::last_mod]
Nov 05, 2024 7:51:30 AM com.broadcom.patchman.client.PatchClient main
INFO: Running PatchClient with arguments: [list, -sort, INSTALLED::UPLOADED::ERROR|-LAST_MOD::-LAST_MOD::-LAST_MOD, ::id::description::state::last_mod]
Nov 05, 2024 7:57:28 AM com.broadcom.patchman.client.PatchClient main

Environment

API Gateway 11.1

Cause

The /boot space was not the issue - the issue was with the kernel.

Resolution

The first install is not in the patches.log but only in the patch_cli.log, which indicates the first install was exceuted from the command line using opt/SecureSpan/PatchManagement/bin/patch.sh <action>. 

The second install was from the ssgconfig menu. 

The first install was still busy when the second install was started and failed on the \boot space. The first installation attempt was never completed and due to this, it was partly applied .

The recommended solution is to rebuild the secondary node and perform the upgrade again.