Phosphor dump manager : Crashed for quota exceeded error

The Problem:

BMC goes into Quiesced state due to the crashing of Phosphor Dump manager for
not being able to handle the exception thrown while capturing core dumps if the
disk quota is full

The Solution:

An exception handling mechanism is put in place to catch any exception thrown
while capturing the dumps, printing the error message and then carry on as
susual.

Test Results:

Oct 12 11:13:44 ever6bmc systemd[1]: Starting Phosphor Dump Manager...
Oct 12 11:13:44 ever6bmc systemd[1]: Started Phosphor Dump Manager.
Oct 12 11:13:44 ever6bmc phosphor-dump-manager[4834]: Core file found, files
size 12
Oct 12 11:13:44 ever6bmc phosphor-dump-manager[4834]: Dump not captured due to a
cap.
Oct 12 11:13:44 ever6bmc phosphor-dump-manager[4834]: Exception received while
capturing dump, xyz.openbmc_project.Dump.Create.Error.QuotaExceeded: Dump not
captured due to a cap.

Signed-off-by: Swarnendu Roy Chowdhury <[email protected]>

Change-Id: Ia38dd0ec91fce5f7c81d4ea3fb5089fd913942dc

Author: Swarnendu-R-C

dump_manager_bmc.cpp

@@ -177,7 +177,18 @@ void Manager::checkAndCreateCoreDump()
             log<level::INFO>(
                 fmt::format("Core file found, files size {}", files.size())
                     .c_str());
-            captureDump(Type::ApplicationCored, files);
+            try
+            {
+                captureDump(Type::ApplicationCored, files);
+            }
+            catch (const std::exception& excp)
+            {
+                log<level::ERR>(
+                    fmt::format("Exception received while capturing dump: "
+                                "{}",
+                                excp.what())
+                        .c_str());
+            }
         }
     }
 }