VxRail: LCM Failed at Error Extracting Update Bundle 7.0.132

Summary: LCM from 4.7.x to 7.0.132 failed at extracting the upgrade bundle, progress ended at 10%.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Troubleshooting steps:

  • Error from VxRail Manager plugin: 
    VxRail Update In Progress: Version 7.0.132-26894200
The update package is successfully transferred to the local system. After it's checked and deployed, you'll be asked to enter necessary information to complete the update process.
VxRail Update ran into a problem...
Error extracting update bundle 7.0.132-26894200. The upgrade engine has been deployed, however it failed to start. Please try again later.
  • From lcm.log, there is a surrogate decommission error: 
    2021-04-07T16:03:05.031+0000 INFO [pool-8-thread-1] com.vce.lcm.helper.SurrogateLcmDeployer SurrogateLcmDeployer.triggerDeployScript:267 - Successfully deployed the surrogate.
2021-04-07T16:08:05.188+0000 INFO [pool-8-thread-1] com.vce.lcm.helper.SurrogateLcmDeployer SurrogateLcmDeployer.restoreDatabase:240 - Decommission surrogate and recover database
2021-04-07T16:08:05.189+0000 INFO [pool-8-thread-1] com.vce.lcm.helper.SurrogateLcmDeployer
SurrogateLcmDeployer.triggerDBRestoreScript:282 - Executing the /data/store2/lcm/bootstrap.sh
2021-04-07T16:08:06.193+0000 INFO [pool-8-thread-1] com.vce.lcm.helper.SurrogateLcmDeployer SurrogateLcmDeployer.triggerDBRestoreScript:284 - Successfully restore the database.
2021-04-07T16:08:06.193+0000 INFO [pool-8-thread-1] com.vce.lcm.helper.SurrogateLcmDeployer SurrogateLcmDeployer.isSurrogateKillSwitchOff:106 - Surrogate kill switch is off
2021-04-07T16:08:06.200+0000 INFO [pool-8-thread-1] com.vce.commons.rest.RestApiClient RestApiClient.postForObject:152 - Sending post request to https://127.0.0.1/undeploy?path=/surrogate with request { }
2021-04-07T16:08:06.313+0000 ERROR [pool-8-thread-1] com.vce.lcm.helper.SurrogateLcmDeployer SurrogateLcmDeployer.decoSurrogateByCatalinaManager:388 -org.springframework.web.client.HttpClientErrorException$Forbidden: 403 : [<!doctype html><html lang="en"><head><title>HTTP Status 403 – Forbidden</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b
color: Color value is invalid
... (431 bytes)]
  • From web.log, the surrogate was deployed successfully but failed to start up in 5 minutes: 
    2021-04-07T16:03:05.032+0000 INFO [pool-8-thread-1] com.emc.mystic.manager.web.util.SurrogateUtil SurrogateUtil.waitForSurrogateStartup:29 - Waiting for Surrogate processor to start up
.
.
2021-04-07T16:08:05.188+0000 WARN [pool-8-thread-1] com.emc.mystic.manager.upgrade.process.BundleDeployProcessService BundleDeployProcessService.deploySurrogate:444 - Surrogate was deployed but failed to start up! Decommission surrogate
  • Looking into the surogate.log, it ends at reading the file /var/lib/vmware-marvin/config-journal.json: 
    2021-04-07 16:03:17,957 INFO [SURROGATE] [Catalina-utility-2] c.d.v.l.d.p.r.ConfigurationJournalRepositoryImpl [ConfigurationJournalRepositoryImpl.java:65] Reading file /var/lib/vmware-marvin/config-journal.json.
  • If there are no more exceptions from the surrogate.log, check more details in the log below at the timestamp of the failure: catalina.0.log and localhost.0.log
      
    <record>
  <date>2021-04-07T16:03:17.992363Z</date>
  <millis>1617811397992</millis>
  <nanos>363000</nanos>
  <sequence>92</sequence>
  <logger>org.apache.catalina.core.StandardContext</logger>
  <level>SEVERE</level>
  <class>org.apache.catalina.core.StandardContext</class>
  <method>startInternal</method>
  <thread>142</thread>
  <message>One or more listeners failed to start. Full details will be found in the appropriate container log file</message>
</record>

  <date>2021-04-07T16:03:17.991585Z</date>
  <millis>1617811397991</millis>
  <nanos>585000</nanos>
  <sequence>91</sequence>
  <logger>org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/surrogate]</logger>
  <level>SEVERE</level>
  <class>org.apache.catalina.core.StandardContext</class>
  <method>listenerStart</method>
  <thread>142</thread>
  <message>Exception sending context initialized event to listener instance of class [org.springframework.web.context.ContextLoaderListener]</message>
  <exception>
    <message>org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'DeployAndUpgradeRestService': Unsatisfied dependency expressed through field 'virtualApplianceUpgradeService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'virtualApplianceUpgradeService': Unsatisfied dependency expressed through field 'lcmService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'LCMServiceImpl': Unsatisfied dependency expressed through field 'bundleTransferService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'bundleTransferServiceImpl': Unsatisfied dependency expressed through field 'managementConnectionService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'managementConnectionServiceImpl': Unsatisfied dependency expressed through field 'vcConnectionService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'VCConnectionServiceImpl': Unsatisfied dependency expressed through field 'connectionService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'connectionHelper': Unsatisfied dependency expressed through field 'mysticClusterReader'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'mysticClusterJpaReader': Unsatisfied dependency expressed through field 'configurationJournalRepository'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configurationJournalRepositoryImpl': Invocation of init method failed; nested exception is com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "uplinkPortId" (class com.vce.commons.core.model.NicProfile), not marked as ignorable (3 known properties: "speedMb", "device", "key"])
 at [Source: (File); line: 1, column: 896] (through reference chain: com.dellemc.vxrail.lcm.data.provider.repositories.model.ConfigurationJournal["hosts"]-&gt;java.util.ArrayList[0]-&gt;com.vce.commons.core.model.VxRailHost["hardwareProfile"]-&gt;com.vce.commons.core.model.HardwareProfile["nicProfileList"]-&gt;java.util.ArrayList[0]-&gt;com.vce.commons.core.model.NicProfile["uplinkPortId"])</message>
    <frame>
      <class>org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement</class>
      <method>inject</method>

 

 

Cause

The config-journal.json file contains some incompatible entries. In this case, it is the "nicProfileList" -- "uplinkPortId": "null "  in "hosts" section 
This unrecognized field will be ignored in a future release.

Resolution

Workaround:
1. For error in LCM to 7.0.132, locate the file config-journal.json on VxRail Manager and rename it as below, retry with bundle uploading, rename it back when upgrade finished:

mv /var/lib/vmware-marvin/config-journal.json /var/lib/vmware-marvin/config-journal.json.bak
 

2. If the same issue encountered when extracting 4.7.x bundles, you must correct the unsupported parameters in config-journal.json and retry.

Affected Products

VxRail, VxRail Software
Article Properties
Article Number: 000185222
Article Type: Solution
Last Modified: 09 May 2026
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.