vCenter server upgrade fails in stage 2 with an error: "A problem occurred while- applying network configuration".
search cancel

vCenter server upgrade fails in stage 2 with an error: "A problem occurred while- applying network configuration".

book

Article ID: 393408

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • While upgrading vCenter server 7.0.x to 8.0.x upgrade fails at 50% in stage 2 when the task copy data from source vCenter server to target vCenter server and encounter a problem while applying network configuration. 
  • Error message: "A problem has occurred. The source vCenter Server might have been Powered Off during this process."

 

  • Logs located in source vCenter server 7.x under location  /var/log/vmware/upgrade/export-upgrade-runner.log show below given errors. 

export-upgrade-runner.log

YYYY-MM-DDTHH:MM:SS.###<Time_Zone> INFO upgrade.states.component_states vcdb:Export: STDERR: /tmp/vmware-upgrade-temp-dir9SX3kFOqyo/tmpxhONC0Xyut/payload/componentPhaseLauncher.py:86: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
YYYY-MM-DDTHH:MM:SS.###<Time_Zone>  INFO upgrade.states.component_states vcdb:Export: STDERR:   import imp
YYYY-MM-DDTHH:MM:SS.###<Time_Zone>  INFO upgrade.states.component_states vcdb:Export: Script completed for 17.188584804534912 secs with return-code='0', and executionId=####d###-##b#-##db-a###-#e#e#e#c#e##

YYYY-MM-DDTHH:MM:SS.###<Time_Zone>  INFO upgrade.states.component_states sso:Export: 2025-03-25T14:27:15.318Z INFO sso.VMwareSSOExporter Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M     -Dcom.sun.org.apache.xml.internal.security.ignoreLineBreaks=true     -Dorg.apache.xml.security.ignoreLineBreaks=true
YYYY-MM-DDTHH:MM:SS.###<Time_Zone>  INFO upgrade.states.component_states sso:Export: Exception in thread "main" java.lang.RuntimeException: The SSL-enabled Connector of legacy Tomcat is missing required attribute: keystoreFile . The SSL configuration cannot be migrated.

 Same error indication observed on the log Export_com.vmware.sso.log

Export_com.vmware.sso.log

YYYY-MM-DDTHH:MM:SS.###<Time_Zone INFO sso.VMwareSSOExporter Picked up JAVA_TOOL_OPTIONS: -Xms32M -Xmx128M     -Dcom.sun.org.apache.xml.internal.security.ignoreLineBreaks=true     -Dorg.apache.xml.security.ignoreLineBreaks=true
Exception in thread "main" java.lang.RuntimeException: The SSL-enabled Connector of legacy Tomcat is missing required attribute: keystoreFile . The SSL configuration cannot be migrated.
at com.vmware.identity.migration.CertUtil.getRequiredAttribute(CertUtil.java:206)

 

Environment

vSphere vCenter server 8.x

vSphere vCenter server 7.x

Cause

  • These errors observed when the source vCenter server has the deprecated feature Integrated Windows Authentication (IWA) enabled and selected the option upgrade data 'configuration and historical data(events and tasks)

Resolution

  •   To continue upgrade in stage 2 need to follow below given steps:

Remove IWA to authenticate AD instead use the Ldap/Ldaps methods and also disjoin domain before start with the upgrade process. 

Ensure not to select the option upgrade data - 'configuration and historical data(events and tasks)' instead select only configuration without historical data.    

Refer to Option 1 as highlighted below,  which excludes tasks and events :              

Configuration and Inventory (X.XX GB) Estimated downtime: XX minutes

Configuration, Inventory, Tasks and Events (X.XX GB)

Configuration, Inventory, Tasks, Events and Performance Metrics (X.XX GB)

Upgrade task will continue to export data from source vCenter server to the destination appliance and the upgrade will succeed. 

Note: In some cases you do not need to remove IWA, instead continue with selecting Configuration and Inventory (X.XX GB) Estimated downtime: XX minutes

Additional Information

Powered by Wolken Software