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

'Failed to authentication with guest OS using supplied credentials' error while Deploy, Upgrade, Migrate or Restore of VCSA 6.5 GA or U1 (51124)

Last Updated: 11/8/2023Categories: TroubleshootingTotal Views: 100383Language:
Chinese (Simplified)JapaneseEnglish

21 like this article

Subscribe to get an email
newsletter with new updates

21 people found this helpful Please provide article feedback:

Symptoms

vCenter Server Appliance (VCSA) or Platform Services Controller (PSC) deployment fails when you try to deploy, upgrade, migrate, or restore to version 6.5.0GA (4602587) and 6.5.0a (4944578).

Note: This does not affect VCSA/PSC 6.5GA or 6.5.0a deployments prior to October 22, 2017 daily operations. Only restoring to 6.5GA or 6.5.0a will trigger this issue.

When you use the impacted build, you will see the following symptoms:

Deployment hangs at 80% during Stage 1 without error message.

The Installer.log file displays similar to:

2017-10-26T15:15:34.596Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
2017-10-26T15:15:34.596Z - debug: [1]pollRpmInstallProgress:getGuestFileErr:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

In the /var/log/messages file of a freshly deployed VCSA, you see similar to:

2017-10-26T15:22:31.720015+00:00 localhost useradd[3196]: pam_unix(useradd:account): expired password for user root (password aged)

2017-10-26T15:22:31.720370+00:00 localhost useradd[3196]: Authentication token is no longer valid; new one required

2017-10-26T15:22:31.720632+00:00 localhost useradd[3196]: failed adding user 'cm', data deleted
2017-10-26T15:22:31.724506+00:00 localhost groupadd[3198]: pam_unix(groupadd:account): expired password for user root (password aged)

2017-10-26T15:22:31.724818+00:00 localhost groupadd[3198]: Authentication token is no longer valid; new one required

2017-10-26T15:22:31.755178+00:00 localhost vaos[1059]: USER PID ACCESS COMMAND

2017-10-26T15:22:31.755413+00:00 localhost vaos[1059]: /var/lib/rpm/Packages:
2017-10-26T15:22:31.762300+00:00 localhost vaos[1059]: 2017-10-26T15:22:31.761Z: RPM Installation failed

In the /var/log/firstboot/cloudvm.log file, you will see similar to:

usermod.bk: group 'cis' does not exist
/usr/sbin/usermod.bk -a -G cis cm
Traceback (most recent call last):
File "/usr/sbin/usermod", line 19, in <module>
errcode = subprocess.check_call(sys.argv)
File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/sbin/usermod.bk', '-a', '-G', 'cis', 'cm']' returned non-zero exit status 6
error: %pre(vmware-cm-6.5.0-4944578.x86_64) scriptlet failed, exit status 1

error: vmware-cm-6.5.0-4944578.x86_64: install failed

Cause

VCSA 6.5 enforces a root password expiration of 365 days from the appliance OS build time.

At this time 6.5GA and 6.5.0a contains an expired root password.

Note: VCSA 6.5U1 will begin experiencing this issue after July 1, 2018.

Resolution

This is a known issue affecting vCenter Server Appliance 6.5.

Note:

This re-released version of vCenter Server Appliance 6.5 has known security issues. These issues are documented in VMware Security Advisories and the release notes for VMware vCenter Server Appliance Photon OS Security Patches. For example the Open Source security issues listed in VMware Security Advisories VMSA-2017-0004 and VMSA-2017-0007 are critical severity and are applicable to vCSA 6.5. VMware recommends adopting the latest version of vCenter Server Appliance 6.5 in order to remediate the known security issues

This table lists the recommended workarounds for VCSA:

VCSA releases

Impacted Build Number

Impact

Recommendation

vCenter Server 6.5 GA

4602587

Cannot be deployed, migrated or restored to.

Apply patches 6.5.0f or 65U1c or later immediately to existing VCSA deployments. For more information, see vCenter Server Appliance 6.5.0f and vCenter Server 6.5 Update 1c Release Notes.

vCenter Server 6.5a

4944578

Cannot be deployed, migrated or restored to.

Apply patches 6.5.0f or 65U1c or later immediately to existing VCSA deployments. For more information, see vCenter Server Appliance 6.5.0f and vCenter Server 6.5 Update 1c Release Notes.

vCenter Server 6.5b

5178943

Cannot be deployed, migrated or restored to after 02/03/2018.

Apply patches 6.5.0f or 65U1c or later immediately to existing VCSA deployments. For more information, see vCenter Server Appliance 6.5.0f and vCenter Server 6.5 Update 1c Release Notes.

vCenter Server 6.5c

5318112

Cannot be deployed, migrated or restored to after 02/03/2018.

Apply patches 6.5.0f or 65U1c or later immediately to existing VCSA deployments. For more information, see vCenter Server Appliance 6.5.0f and vCenter Server 6.5 Update 1c Release Notes.

vCenter Server 6.5d

5318154

Cannot be deployed, migrated or restored to after 02/03/2018.

Apply patches 6.5.0f or 65U1c or later immediately to existing VCSA deployments. For more information, see vCenter Server Appliance 6.5.0f and vCenter Server 6.5 Update 1c Release Notes.

vCenter Server 6.5e

5705665

Cannot be deployed, migrated or restored to after 02/03/2018.

Apply patches 6.5.0f or 65U1c or later immediately to existing VCSA deployments. For more information, see vCenter Server Appliance 6.5.0f and vCenter Server 6.5 Update 1c Release Notes.

vCenter Server 6.5 U1

5973321

Cannot be deployed, migrated or restored to after 07/01/2018.

Apply patches 65U1c or later immediately to existing VCSA deployments. For more information, see vCenter Server 6.5 Update 1c Release Notes.

vCenter Server 6.5 U1a

6671409

Cannot be deployed, migrated or restored to after 8/14/2018.

Apply patches 65U1c or later immediately to existing VCSA deployments. For more information, see vCenter Server 6.5 Update 1c Release Notes.

vCenter Server 6.5 U1b

6816762

Cannot be deployed, migrated or restored to after 9/26/2018.

Apply patches 65U1c or later immediately to existing VCSA deployments. For more information, see vCenter Server 6.5 Update 1c Release Notes.

Related Information

Resolution if entries similar to: debug: initiatefiletransferfromguest error: serverfaultcode: failed to authenticate with the guest operating system using the supplied credentials
vCenter Server Appliance 6.5 GA または U1 リリースへのデプロイ、アップグレード、移行、またはリストアが失敗する (52673)
简体中文：部署、升级、迁移或还原到 vCenter Server Appliance 6.5 GA 或 U1 版本失败

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

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.5.x

Take Our Survey

Support Assistant