Manual upgrade of NSX Host VIBs pauses with "Invalid Version" error
search cancel

Manual upgrade of NSX Host VIBs pauses with "Invalid Version" error

book

Article ID: 421230

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • You are attempting to upgrade NSX VIBs on hosts using one of the following methods:
  • You did not click the STAGE button on the Host Upgrade page in the NSX Manager UI prior to performing the upgrade.

  • One error is displayed in the Upgrade Status for the affected host on the Host Upgrade page.


  • The NSX Configuration status of the affected host shows "Install Failed". Clicking "Install Failed" reveals an error message similar to the following:

    Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-monitoring.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-vdpi.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-shared-libs.Node has invalid version 2.6.1-19195979 of software nsx-python-protobuf.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-proxy.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-netopa.Node has invalid version 0.4.14.py35-19345965 of software nsx-python-greenlet.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-python-utils.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-nestdb.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-esx-datapath.Node has invalid version 1.3.5.py35-22202305 of software nsx-python-gevent.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-python-logging.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-context-mux.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-exporter.Node has invalid version 4.2.2.1.0-7.0.24765085 of software vsipfwlib.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-ids.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-sfhc.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-opsagent.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsxcli.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-cpp-libs.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-proto2-libs.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-adf.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-platform-client.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-cfgagent.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-host.Node has invalid version 4.2.2.1.0-7.0.24765085 of software nsx-mpa.

     

  • You see similar messages in /var/log/nsxapi.log on NSX Manager:
    <Timestamp>  INFO messaging-lib-executor- SFHCServiceImpl 17821 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Successfully processed operation status message ( class=com.vmware.nsx.sfhc.ServiceFabricMessage.SfhcMessage, toStr=message_type: MT_OPERATION_STATUS
operation_id: "<OP_UUID>"
service_fabric_object {
  software {
    name: "nsx-monitoring"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-vdpi"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-shared-libs"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-python-protobuf"
    version: "2.6.1-19195979"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-proxy"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-netopa"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-python-greenlet"
    version: "0.4.14.py35-19345965"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-python-utils"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-nestdb"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-esx-datapath"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-python-gevent"
    version: "1.3.5.py35-22202305"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-python-logging"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-context-mux"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-exporter"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "vsipfwlib"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-ids"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-sfhc"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-opsagent"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsxcli"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-cpp-libs"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-proto2-libs"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-adf"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-platform-client"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-cfgagent"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-host"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
service_fabric_object {
  software {
    name: "nsx-mpa"
    version: "4.2.2.1.0-7.0.24767647"
    state: INVALID_VERSION
  }
}
return_same_correlationid: true
 ) from host <TN_UUID> operationId <OP_UUID>
<Timestamp>  INFO org.corfudb.runtime.collections.streaming.StreamPollingScheduler-worker-2 SFHCServiceImpl 17821 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] SFHC request completed. MessageType MT_SOFTWARE_STATUS, operationId <OP_UUID>, clientId <TN_UUID>
<Timestamp>  INFO org.corfudb.runtime.collections.streaming.StreamPollingScheduler-worker-2 HostPrepServiceFabricDeploymentServiceImpl 17821 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Software issues: [26]. Updating the installation status of host <TN_UUID> to INSTALL_FAILED
<Timestamp>  INFO org.corfudb.runtime.collections.streaming.StreamPollingScheduler-worker-2 DeploymentUnitInstanceServiceImpl 17821 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updating the deploymentProgressState for deploymentUnitInstance: DeploymentUnitInstance [ id=DeploymentUnitInstance/<DU_UUID>, deploymentUnitId=DeploymentUnit/<DU_UUID>, hostId=HostTransportNode/<TN_UUID>, entityId=null, prevEntityId=null, runningVersion=3.2.2.0.0.20737303, deploymentProgressState=INSTALL_FAILED, deploymentGoalState=ENABLED, internalLastKnownOSVersion=7.0.3, agentId=null, errorId=26178, errorMessage=] to INSTALL_FAILED:

Environment

VMware NSX

Cause

If the staging process is skipped, the NSX Manager fails to correctly recognize the target upgrade version. Consequently, after the VIBs are upgraded on the host, the NSX Manager incorrectly flags the installed software as an "Invalid Version".

Resolution

To resolve this issue, perform the following steps:

  1. Navigate to the Host Upgrade page in the NSX Manager UI and click the STAGE button to initiate the staging process.
  2. Log in to the affected ESXi host as root via the CLI and restart the nsx-sfhc service using the command below. Note: Restarting this service is non-disruptive and will not impact production traffic.
    /etc/init.d/nsx-sfhc restart
  3. Return to the Host Upgrade page in the NSX Manager UI and click RUN POST CHECK to verify that the error has been resolved.
Powered by Wolken Software