Keep original istep error log during reconfig loops

The original istep log may contain useful information that we
don't have in the reconfig log.  Instead of deleting it, just
commit it as INFO.

Change-Id: I7cd031997665d70227579b22701ed063d4f81bb5
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/64275
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Reviewed-by: Richard J. Knight <rjknight@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Reviewed-by: Marshall J. Wilks <mjwilks@us.ibm.com>
Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>

1 files changed, 5 insertions, 1 deletions

diff --git a/src/usr/initservice/istepdispatcher/istepdispatcher.C b/src/usr/initservice/istepdispatcher/istepdispatcher.C
index ec71a59cd..a0ca4d4c7 100644
--- a/src/usr/initservice/istepdispatcher/istepdispatcher.C
+++ b/src/usr/initservice/istepdispatcher/istepdispatcher.C
@@ -597,7 +597,11 @@ errlHndl_t IStepDispatcher::executeAllISteps()
                         // be replaced by the ReconfigLoop info error with the
                         // same plid that matches the real errors
                         l_plid = err->plid();
-                        delete err;
+
+                        // Commit the istep log as informational since it
+                        // might include some useful information
+                        err->setSev(ERRORLOG::ERRL_SEV_INFORMATIONAL);
+                        errlCommit(err, INITSVC_COMP_ID);
                         err = NULL;
                     }