Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 12501Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

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.

You will see similar log entries in the below log file:

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.

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 patching fails to update the 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@vcsa1 [ ~ ]# 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)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server のデプロイ中の CEIP 設定の不一致が原因で、VMware Directory Service (VMDIRD) がリカバリ不能な状態になる (76646)

KB
•
在全新安装或升级到 ESXi 6.7 Update 3 后，ESXi 主机可能无法在 UEFI 模式下引导 (76159)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant