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

Commission of a node in VMware Cloud Foundations 3.5.1 fails on "Configures DNS Server IPs on Given Hosts" task (76359)

Last Updated: 3/26/2024Categories: TroubleshootingTotal Views: 2784Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Commission of a node  fails on "Configures DNS Server IPs on Given Hosts" task with error messages "HOST_DNS_CONFIGURATION_FAILED Cannot configure DNS on host".

Similar errors messages as seen below are found in /var/log/vmware/vcf/operationsmanager/operationsmanager.log

2019-10-07 13:27:32.125 [vcf_om,c1151769a931b0d4,63498fe3ff22f45f] [-thread-11] DEBUG [c.v.v.hostmanager.comm.action.ConfigureDnsAction] <83b7cd40-e905-11e9-8177-e92dab19c32b> Nslookup command extract DNS Server: 150.80.1.5 server
2019-10-07 13:27:32.125 [vcf_om,c1151769a931b0d4,63498fe3ff22f45f] [-thread-11] ERROR [c.v.v.hostmanager.comm.action.ConfigureDnsAction] <83b7cd40-e905-11e9-8177-e92dab19c32b> nslookup output validation failed. DNS [150.80.1.5, 150.80.1.6] configuration failed on the host 10.10.13.20.
2019-10-07 13:27:32.127 [vcf_om,c1151769a931b0d4,63498fe3ff22f45f] [-thread-11] DEBUG [ com.vmware.evo.sddc.common.util.SshUtil] <83b7cd40-e905-11e9-8177-e92dab19c32b> Destroyed the ssh Session
2019-10-07 13:27:32.140 [vcf_om,c1151769a931b0d4,63498fe3ff22f45f] [-thread-11] ERROR [c.v.e.sddc.orchestrator.model.error.ErrorFactory] [DLBFK7] HOST_DNS_CONFIGURATION_FAILED Cannot configure DNS [150.80.1.5, 150.80.1.6] on host 10.10.13.20

The SDDC manager in not able to parse the output of the '"nslookup " command and we are getting error messages "nslookup command output is empty"

2019-10-07 13:22:57.557 [vcf_om,c1151769a931b0d4,63498fe3ff22f45f] [-thread-11] DEBUG [ com.vmware.evo.sddc.common.util.SshUtil] <83b7cd40-e905-11e9-8177-e92dab19c32b> Starting to execute command [nslookup 10.10.13.20 ]
2019-10-07 13:22:57.609 [vcf_om,c1151769a931b0d4,63498fe3ff22f45f] [-thread-11] DEBUG [ com.vmware.evo.sddc.common.util.SshUtil] <83b7cd40-e905-11e9-8177-e92dab19c32b> End of execution of command [nslookup 10.10.13.20], Status: 0
Output:
Error output:
Command timed out: false
2019-10-07 13:22:57.609 [vcf_om,c1151769a931b0d4,63498fe3ff22f45f] [-thread-11] ERROR [c.v.v.hostmanager.comm.action.ConfigureDnsAction] <83b7cd40-e905-11e9-8177-e92dab19c32b> nslookup command output is empty. DNS [150.80.1.5, 150.80.1.6] configuration failed on the host 10.10.13.20.
2019-10-07 13:22:57.609 [vcf_om,c1151769a931b0d4,63498fe3ff22f45f] [-thread-11] DEBUG [c.v.v.hostmanager.comm.action.ConfigureDnsAction] <83b7cd40-e905-11e9-8177-e92dab19c32b> DNS configuration postvalidation:wait for 30000 miliseconds before retrying

The Nslookup  of the host FQDN and the Reverslookup of the host IP address from the SDDC manager and the host itself completed successfully.

The host is configured with the correct DNS serverer

[root@host1:~] cat /etc/resolv.conf
nameserver 150.80.1.5
nameserver 150.80.1.6

​Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This is a known issue affecting VMware Cloud Foundation 3.5.x and the fix is to upgrade to VCF 3.7.0.

Resolution

This issue is resolved VMware Cloud Foundation version 3.7.0.

Workaround

Use the following steps to apply a patch in case an upgrade to VCF 3.7.0 is not an option and only if the current  VCF deployment is on version  3.5.1.

Download the operationsmanager_3.5.1-14878133.zip file attache to the KB.

Use a file transfer utility to copy the operationsmanager_3.5.1-14878133.zip file to the /tmp directory on the SDDC Manager VM.

SSH to the SDDC Manager Controller VM as the vcf user.

Issue the following command to switch to the root user account:

# su

Extract the contents of the operationsmanager_3.5.1-14878133.zip file by issuing the following command:

# unzip -d /tmp /tmp/operationsmanager_3.5.1-14878133.zip

Issue the following command to stop the Operations Manager service:

# systemctl stop operationsmanager

Make a copy of the /opt/vmware/vcf/operationsmanager/vcf-operations-manager.jar file by issuing the following command:

# cp -p /opt/vmware/vcf/operationsmanager/vcf-operations-manager.jar /opt/vmware/vcf/operationsmanager/vcf-operations-manager.jar.bak$(date +%Y%m%d)

Replace the original /opt/vmware/vcf/operationsmanager/vcf-operations-manager.jar file with the version extracted in Step 4 by issuing the following command:

# cp  /tmp/operationsmanager_3.5.1-14878133/vcf-operations-manager.jar /opt/vmware/vcf/operationsmanager/

Change the ownership and permissions on the /opt/vmware/vcf/operationsmanager/vcf-operations-manager.jar file by issuing the following commands:

# chown vcf_operationsmanager:vcf /opt/vmware/vcf/operationsmanager/vcf-operations-manager.jar
# chmod 744 /opt/vmware/vcf/operationsmanager/vcf-operations-manager.jar

Issue the following command to start the Operations Manager service:

# systemctl start operationsmanager

Note: It may take two to three minutes for the Operations Manager service to be functional after starting.

Issue the following command to validate the state of the Operations Manager service. The Operations Manager status should be ACTIVE and the version is updated to "3.5.1-RELEASE-14878133":

# curl http://localhost/operationsmanager/about | json_pp

{
"description" : "Operations Manager",
"version" : "3.5.1-RELEASE-14878133",
"status" : "ACTIVE",
"serviceUrl" : "http://127.0.0.1/operationsmanager",
"name" : "OPERATIONS_MANAGER",
"id" : "3654b774-9ba0-4bc2-970f-cfd94ed84c43"
}

After applying the patch, the following steps must be completed prior to upgrading to a new VMware Cloud Foundation version:

Log in to the SDDC Manager VM as the vcf user and then switch to the root user by typing su -.

Issue the following command to make a copy of the /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml file:

# cp -fp /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml.$(date +%Y%m%d)

Open the /opt/vmware/vcf/lcm/lcm-app/conf/VersionAlias.yml file with a text editor and add the following to the end of the file.

OPERATIONS_MANAGER:
- base: 3.5.1-RELEASE-12050813
alias:
- 3.5.1-RELEASE-14878133

Note: Ensure that only spaces are used when editing VersionAlias.yml file as tab characters will break parsing and the LCM service may not start. Refer to commented examples in the file for a proper sample.

Save and close the file.

Issue the following command to restart the lcm service:

# systemctl restart lcm

Run the following command from SDDC Manager VM and make a note of the 'id'.

# curl localhost/inventory/vcfservices | json_pp

Example:

{
"status" : "ACTIVE",
"description" : "Operations Manager",
"name" : "OPERATIONS_MANAGER",
"version" : "3.5.1-RELEASE-12050813",
"serviceUrl" : "http://127.0.0.1/operationsmanager",
"id" : "5eac87b3-c289-4dec-b1a7-d35a3bfe8e55"
},

Run the following command to update the Operations Manager version value in the SDDC Manager inventory with the new version after applying the patch:

#  cqlsh --cqlversion=3.4.4 -e "update inventory.vcfservice set version='<OPERATIONS_MANAGER_Version>' where id='<OPERATIONS_MANAGER_ID>';"

Notes:

Replace this version with version value obtained from Step 6.

Replace the 'id' with the 'id' value obtained step 6.

Example:

cqlsh --cqlversion=3.4.4 -e "update inventory.vcfservice set version='3.5.1-RELEASE-14878133' where id='5eac87b3-c289-4dec-b1a7-d35a3bfe8e55';"

Verify the Operations Manager version was changed to “3.5.1-RELEASE-14878133" by running the command:

curl localhost/inventory/vcfservices | json_pp’

Example:
{
"id" : "5eac87b3-c289-4dec-b1a7-d35a3bfe8e55",
"status" : "ACTIVE",
"name" : "OPERATIONS_MANAGER",
"description" : "Operations Manager",
"version" : "3.5.1-RELEASE-14878133",
"serviceUrl" : "http://127.0.0.1/operationsmanager"
}

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

operationsmanager_3.5.1-14878133

Additional Resources

KB
•
在 vRealize Automation 7.x 中禁用 Internet Information Services (IIS) 应用程序池回收 (76333)

KB
•
Application Remote Collector が再起動後、7.5 から 8.0 に自動的にアップグレードされる (76412)

KB
•
VMware HCX Enterprise アプライアンスで ntpq コマンドを実行すると、リクエストがタイムアウトする (76290)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 3.5.x

Take Our Survey

Support Assistant