Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Upgrading to VMware vSphere Storage Appliance 5.1 fails after recovering the vSphere Storage Appliance cluster (2033916)

Symptoms

  • Cannot upgrade from VMware vSphere Storage Appliance 1.0 to 5.1
  • Upgrading from VMware vSphere Storage Appliance 1.0 to 5.1 fails
  • This issue occurs after restoring the cluster in vSphere Storage Appliance Manager
  • Log files contain entries similar to:

    svaInstUtil: VMInstSystem::ShellExecuteWait::Execute Res: 0
    svaInstUtil: VMInstSystem::ShellExecuteWait::WAIT_OBJECT_0
    svaInstUtil: VMInstSystem::ShellExecuteWait::GetExitCodeProcess Process: 716 ExitCode: 102 Res: 1
    svaInstUtil: VMInstError::LogErrorLast::Error: 102 (The semaphore is set and cannot be closed. )
    svaInstUtil: VMInstSystem::ShellExecuteWait::done (wait) Res: 102
    svaInstUtil: ExecuteCmd::done Res: 102
    svaInstUtil: GetVCRegisterError::The specified user name or password is wrong Res: 102
    svaInstUtil:  ExecuteVCParamsEx::done Res: 29453
    svaInstUtil:  ExecuteVCData::done Res: 29453
    svaInstUtil:  ExecuteVC::done Res: 29453
    svaInstUtil:  VMInstMsi::GetPropertyString::[UILevel]=
    svaInstUtil: VMInstMsi::PostMsg::Type: 0x01000030 Error: 29453 Value:
    svaInstUtil: VMInstMsi::PostMsg::done Res: 1
    svaInstUtil: RegisterVCServer::VC NOT REGISTERED
    svaInstUtil: RegisterVCServer::done Res: 29453

    ...

    svaInstUtil: VMInstSystem::ShellExecuteWait::WAIT_OBJECT_0
    svaInstUtil: VMInstSystem::ShellExecuteWait::GetExitCodeProcess Process: 756 ExitCode: 0 Res: 1
    svaInstUtil: VMInstSystem::ShellExecuteWait::done (wait) Res: 0
    svaInstUtil: ExecuteCmd::done Res: 0
    svaInstUtil: ExecuteVCParamsEx::done Res: 0
    svaInstUtil: ExecuteVCData::done Res: 0
    svaInstUtil: ExecuteVC::done Res: 0
    svaInstUtil: RegisterVCServer::VC REGISTERED
    svaInstUtil: RegisterVCServer::done Res: 0

    ...

    [UpgradeUtils] [main] INFO - Waited 260 seconds so far for VSA service at 10.150.43.172
    [UpgradeUtils] [main] INFO - Waited 280 seconds so far for VSA service at 10.150.43.172
    [UpgradeUtils] [main] INFO - Waited 300 seconds so far for VSA service at 10.150.43.172
    [VerifyUpgrade] [main] ERROR - Failed to verify version for VSA 10.150.43.172 :: Unable to login
    com.vmware.sva.manager.exception.LoginFailedException: Unable to login
     at com.vmware.sva.manager.service.ClusterService.loginSVA(ClusterService.java:150)
     at com.vmware.sva.upgrade.UpgradeUtils.getSvaService(UpgradeUtils.java:159)
     at com.vmware.sva.upgrade.UpgradeUtils.getSvaService(UpgradeUtils.java:143)
     at com.vmware.sva.upgrade.VerifyUpgrade.verifySVAVMVersions(VerifyUpgrade.java:213)
     at com.vmware.sva.upgrade.VerifyUpgrade.verify(VerifyUpgrade.java:128)
     at com.vmware.sva.upgrade.VerifyUpgrade.main(VerifyUpgrade.java:362)
    Caused by: org.apache.axis2.AxisFault: Connection timed out: connect
     at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
     at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:203)
     at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
     at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
     at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
     at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
     at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
     at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
     at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
     at com.vmware.sva.messaging.ws.sva.SvaserviceStub.login(SvaserviceStub.java:823)
     at com.vmware.sva.manager.service.SvaMessagingService.login(SvaMessagingService.java:82)
     at com.vmware.sva.manager.service.ClusterService.loginSVA(ClusterService.java:148)
     ... 5 more
    Caused by: java.net.ConnectException: Connection timed out: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:529)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:564)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(SSLSocketImpl.java:406)
     at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:123)
     at com.vmware.vim25.util.EasySSLProtocolSocketFactory.createSocket(EasySSLProtocolSocketFactory.java:150)
     at org.apache.commons.httpclient.protocol.ControllerThreadSocketFactory$1.doit(ControllerThreadSocketFactory.java:91)
     at org.apache.commons.httpclient.protocol.ControllerThreadSocketFactory$SocketTask.run(ControllerThreadSocketFactory.java:158)
     at java.lang.Thread.run(Thread.java:662)
    [VerifyUpgrade] [main] INFO - Verify upgrade exited with exit code 5

Cause

When restoring a vSphere Storage Appliance cluster in vSphere Storage Appliance Manager, the vCenter Server must be reinstalled (along with vSphere Storage Appliance Manager) or the original vSphere Storage Appliance datacenter must be deleted. This deletes the vSphere Storage Appliance virtual machine information from the vCenter Server database, including the original vApp parameters. The vApp parameters are typically used to assign the vSphere Storage Appliance servers' front-end addresses.

Resolution

The vApp properties must be restored to the  VMware vSphere Storage Appliance virtual machines for the upgrade to succeed.
 
To restore the vApp properties:
  1. Enable operations of the vSphere Storage Appliance virtual machines and restore vApp properties to vSphere Storage Appliance virtual machines. For more information, see Reconfiguring VSA Network fails after Recovering VSA Cluster (2014714).
  2. Assign the correct IP addresses to virtual machines. For each virtual machine:

    1. Right-click the virtual machine and click Edit Settings.

    2. Click the Options tab.

    3. Click Properties under vApp Options. The properties appear on the right side of the window.

    4. Enter the correct IP address/Netmask/Gateway. You can leave the DNS entry empty.

    5. Click OK.

  3. Power on the VSA VMs.
  4. Verify that the 3 appliances or 2 appliances and VSA Cluster Service display ONLINE on the VSA tab.
  5. Verify that the 2 or 3 VSA datastores appear ONLINE on the VSA tab.
  6. Perform the upgrade.

See Also

Update History

09/11/2012 - Added log samples to symptoms

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 1 Ratings
Actions
KB: