'Latest updates already installed on vCSA, Nothing to stage/install' while updating from VCSA 6.5 to 6.5 U2d in VAMI Page
search cancel

'Latest updates already installed on vCSA, Nothing to stage/install' while updating from VCSA 6.5 to 6.5 U2d in VAMI Page

book

Article ID: 338150

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
  • Using the vCenter Appliance Management Interface (VAMI) to check for updates on vCenter Server Appliance 6.5 U1d and below does not show any available updates.
  • Updates unavailable while upgrading vCenter Server Appliance 6.5 to 6.5 Update 2d
  • In VAMI UI and appliance shell, you see a message similar to:
Latest updates already installed on vCSA, Nothing to stage/install


Environment

VMware vCenter Server Appliance 6.5.x

Cause

This issue occurs due to the method the vCenter Server Appliance (VCSA) 6.5 update feature processes build numbering prior to VCSA 6.5 U1d.

Notes:
  • Upgrades from VCSA 6.5 to VCSA 6.7 are not affected.
  • vCenter Server 6.5 on Microsoft Windows is not affected

Resolution

This is a known issue affecting vCenter Appliance 6.5.x.

Ccurrently, there is no resolution.

Workaround:
To workaround this issue, apply the fix to the existing appliance  manually:
  1. Log in as root via SSH or console session in vCenter Server Appliance.
  2. Run the command to enable the shell.
shell
  1. Download the 59659_changebuild.sh script attached to this article, located on the right hand side of the Web page, click the file to download to your local machine.
Note: For information on using WinSCP to relocate files from a workstation to the vCenter Appliance, see Error when uploading files to vCenter Server Appliance using WinSCP 
       4. Change the file name to changebuild.sh and copy it to /root  on the vCenter  Server Appliance.
cp 59659_changebuild.sh /root/changebuild.sh
 
      5.Run the command to execute permission:
chmod +x /root/changebuild.sh
  1. Run the command to execute the script:
/root/changebuild.sh
  1. Proceed with the update.


Attachments

59659_changebuild.sh get_app