Symptoms

The VxRail Manager "profile_lg" check analyzes the profile log files for incorrectly formatted events. If necessary, this check can correct detected issues in the log file.For example, one event that is being checked for is: UPGRAD_AFTER_UPGRADE_SUCCESS, which should be listed as UPGRADE_AFTER_UPGRADE_SUCCESS The test produces one of the following results: Test ResultResult codeResult Interpretation Pass 0 No issues were found in the profile log. Warning 1 UPGRAD_AFTER_UPGRADE found in profile.log.x and must be corrected _Fixed 1 UPGRAD_AFTER_UPGRADE has been corrected in "profile.log" Failure This test has no failure result Critical This test has no critical result. Every test that passes is not listed in the summary report, for ease of reading.An example of the health-check output is shown below: #========================#======#=========#====================================================================#==============# | Hostname / Category |Status Dell_KB | Warnings or Failures, unless tests Passed ; Product S.N. | #========================#======#=========#====================================================================#==============# | VxRM | _Fixed | profile_lg: UPGRAD_AFTER_UPGRADE replaced in profile.log |

Cause

Upgrades for VxRail, which have previously run release 4.7, may contain a profile.log entry such as: 2022-01-31T23:24:15.751+0000, [pool-8-thread-1], UPGRAD_AFTER_UPGRADE_SUCCESS,VXRAIL_COMPOSITE-4.7.540-27298275_for_4.7.x.zip,,Finished process afterUpgradeSuccess,1643671455751 The path for this file is: /var/log/mystic/profile.log Older versions of the file have an additional suffix, such as ".1" or ".2".The entry above can cause upgrades to fail with the event: No enum constant com.vce.commons.profiler.profilelogging.LCMProfileStep.UPGRAD_AFTER_UPGRADE_SUCCESS

Resolution

Running VxVerify x.40.913 or above (using the Upgrade healthcheck profile), should automatically correct these log entries. Refer to article: VxRail: How to Run the VxVerify Tool Alternatively, edit /var/log/mystic/profile.log and correct the line containing "UPGRAD_" to "UPGRADE_", which is probably the last line in the log.

Support Cases