NSX Upgrade Pre-check Failure: Error 30265 - Edge Node Realization Pending or Failed
search cancel

NSX Upgrade Pre-check Failure: Error 30265 - Edge Node Realization Pending or Failed

book

Article ID: 447330

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • When running the Check Upgrade Readiness pre-checks for a VMware NSX upgrade, a failure is reported for one or more Edge Transport Nodes.

  • The following error is observed in the UI:
    • Error Code: 30265 - Edge node <UUID> has either realization pending or realization failed.

  • In the NSX UI under System > Fabric > Nodes, the Edge Node Configuration State is stuck in In Progress.

  • The following error appears in /var/log/upgrade-coordinator/upgrade-coordinator.log
    [PUC] Pre-upgrade check InspectionTaskInfo[id=edgeNodeRealizationErrorCheck,name=Check for edge node realization error in upgrade groups.] failed 
    ...
    failures=[{"moduleName":"upgrade-coordinator","errorCode":30265,"errorMessage":"Edge node <UUID> has either realization pending or realization failed."}]

Environment

VMware NSX

Cause

The Edge Transport Node configuration state is either failed or stuck in CONFIG_STATUS_IN_PROGRESS within the Corfu database. This prevents the Upgrade Coordinator from verifying that the node is in a stable state ready for the upgrade.

Resolution

This issue can be resolved by manually synchronizing the node configuration from the NSX Manager UI:

  1. UI Resync (Primary Method):

    1. Navigate to System > Fabric > Nodes > Edge Transport Nodes.
    2. Select the problematic Edge Node.
    3. Click Actions > Sync Edge Node Configuration.
    4. If the status remains stuck, select the node, click Edit, and then click Save without making changes to trigger a refresh.
  2. Verify Status via CLI:

    1. Log in to the NSX Manager CLI as root.
    2. Run the following command to check the realization state:
      /opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -t TransportNodeState -o showTable
    3. Ensure the hostConfigStatus for the affected UUID is CONFIG_STATUS_SUCCESS.

     3. Rerun Precheck:

    • Once the node shows as Success or Up in the UI, return to the Upgrade wizard and rerun the prechecks.

 

Additional Information

If you believe you have encountered this issue and the above resolution is not working, open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.