"Unexpected content in /etc/issue file" - VCSA patching succeeded but failed to update the VAMI build

Products

• VMware vCenter Server

Issue/Introduction

• After patching VCSA build on UI shows the new build but on VAMI it is still old.
• VAMI update page still shows the same version available for update/patching.
• Below logs would be noticed in /var/log/vmware/applmgmt/software-packages.log



  DEBUG:vmware.vherd.base.software_update:Packages updated successfully
  DEBUG:vmware.vherd.base.software_update:/var/vmware/applmgmt/patch-history/ directory created successfully
  INFO:vmware.vherd.base.software_update:Setting appliance version to 6.7.0.xxxxx build xxxxxx
  ERROR:vmware.vherd.base.software_update:Got exception while trying to save metadata to a file: Unexpected content in /etc/issue file.

  
  
  
• Patching succeeds but the VAMI shows the old build.
  via CLI :
  

  Setting appliance version to 6.7.0.xxxxx build xxxxxxx
  Got exception while trying to save metadata to  a file: Unexpected content in /etc/issue file.xxxx
  Packages upgraded successfully, Reboot is required to complete the installation.

  
  

Environment

VMware vCenter Server Appliance 6.7.x
VMware vCenter Server Appliance 7.x

Cause

When we update the banner by updating the /etc/issue option in advance settings or modify the /etc/issue file directly from the default, the vCSA patching fails to update the vCSA VAMI build.

Resolution

This issue is resolved in VMware vCenter Server 6.7 Update 3g (build number 16708996).
This issue is resolved in VMware vCenter Server 7.0 Update 1 (build number 16860138).

Workaround:
To workaround this issue follow the steps below:

• Modify the /etc/issue file to the original before patching.

The file '/etc/issue' contents can be customized but the defaults lines which has the version number and deployment type must be kept for patching to succeed.

• Check the VAMI page for product version and type and update the /etc/issue file accordingly.

Example: /etc/issue  :: (Original Content from a LAB).
Note line 1 and 3 should be blank. Line 2 will have the version and line 4 will have the deployment type, as shown in the below example:

root@vchostname [ ~ ]# less -N /etc/issue
      1
      2 VMware vCenter Server Appliance 6.7.0.31000
      3
      4 Type: vCenter Server with an external Platform Services Controller
      5
/etc/issue (END)

Additional Information

The /etc/issues displays a banner during an SSH login session, this means that you will see the message during the login.
The /etc/motd displays a banner after a successful SSH login.