Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

VMware Cloud Foundation update fails during VRM update when Log Insight was manually upgraded (67228)

Last Updated: 8/25/2021Categories: TroubleshootingTotal Views: 2967Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Log Insight was manually upgraded outside of VMware Cloud Foundation.

VMware Cloud Foundation upgrade fails during LCM upgrade.

You see similar entries in the /home/vrack/vrm/logs/evosddc-upgrade.log on the SDDC Manager Controller VM:

2018-11-29 23:01:25 [pool-22-thread-1] DEBUG c.v.v.v.u.u.vrli.VRLINtpConfigurator - Request body: {"timeReference": "NTP_SERVER","ntpServers": ["10.x.x.x","10.x.x.x"]}
2018-11-29 23:01:26 [pool-22-thread-1] ERROR c.v.v.v.u.u.vrli.VRLINtpConfigurator - POST request to vRLI loginsight-cluster.vcf.vmware.corp failed. Response code 404
2018-11-29 23:01:26 [pool-22-thread-1] ERROR c.v.v.vrm.upgrade.task.UpdateNtps - Error: Failed post request in vRLI {}
com.vmware.vrack.vrm.upgrade.NtpConfigurationException: Failed post request in vRLI
at com.vmware.vrack.vrm.upgrade.utils.vrli.VRLINtpConfigurator.postRequest(VRLINtpConfigurator.java:104)
at com.vmware.vrack.vrm.upgrade.task.UpdateNtps.queryAndUpdateOverApi(UpdateNtps.java:440)
at com.vmware.vrack.vrm.upgrade.task.UpdateNtps.updateNtpsForVRLI(UpdateNtps.java:279)
at com.vmware.vrack.vrm.upgrade.task.UpdateNtps.executeUpgradeTask(UpdateNtps.java:194)
at com.vmware.vrack.vrm.upgrade.task.core.UpgradeTask$1.call(UpgradeTask.java:82)
at com.vmware.vrack.vrm.upgrade.task.core.UpgradeTask$1.call(UpgradeTask.java:76)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2018-11-29 23:01:26 [pool-22-thread-1] ERROR c.v.v.vrm.upgrade.task.UpdateNtps - Failed to set Ntps
com.vmware.vrack.vrm.upgrade.UpgradeException: com.vmware.vrack.vrm.upgrade.NtpConfigurationException: Failed post request in vRLI

Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.

Cause

Due to API changes between Log Insight versions, Cloud Foundation is not able to update NTP settings within Log Insight.

Resolution

This is a known issue affecting VMware Cloud Foundation. There is currently no resolution.

Workaround

Take a snapshot of the SDDC Manager Controller VM.

SSH to the SDDC Manager Controller VM.

Issue the following command to obtain the relevant Log Insight information from the cassandra database:

/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "select * from vrmkeyspace.loginsight"

Note: You will see output similar to the following:

id                                   | adminemail | createddate              | dalversion | enhancedloggingenabled | externalloginsightserveraddress | externalsyslogserveraddress | hostname                       | ipaddress     | modifieddate             | name            | scope  | state | vipaddress    | vipfqdn                           | vmsize
--------------------------------------+------------+--------------------------+------------+------------------------+---------------------------------+-----------------------------+--------------------------------+---------------+--------------------------+-----------------+--------+-------+---------------+-----------------------------------+--------
87748610-6a87-11e8-a2d7-55408a7195d1 |       null | 2018-06-07 22:56:33+0000 |          1 |                  False |                            null |                        null | loginsight-vm-1.vcf.corp.local | 192.x.x.x | 2018-06-07 22:56:33+0000 | loginsight-vm-1 | public |  null | 192.x.x.x | loginsight-cluster.vcf.corp.local | xsmall
8774ad21-6a87-11e8-a2d7-55408a7195d1 |       null | 2018-06-07 22:56:33+0000 |          1 |                   null |                            null |                        null | loginsight-vm-3.vcf.corp.local | 192.x.x.x | 2018-06-07 22:56:33+0000 | loginsight-vm-3 | public |  null |          null |                              null | xsmall
8774ad20-6a87-11e8-a2d7-55408a7195d1 |       null | 2018-06-07 22:56:33+0000 |          1 |                   null |                            null |                        null | loginsight-vm-2.vcf.corp.local | 192.x.x.x | 2018-06-07 22:56:33+0000 | loginsight-vm-2 | public |  null |          null |                              null | xsmall

Note: Make a note of the id value for each row as it will be used in a later step.

Copy the output and save it somewhere as it will be used to repopulate the database in a later step.

Issue commands similar to the following to remove the Log Insight records from the cassandra database:

/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "delete from loginsight where id=87748610-6a87-11e8-a2d7-55408a7195d1"
/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "delete from loginsight where id=8774ad21-6a87-11e8-a2d7-55408a7195d1"
/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "delete from loginsight where id=8774ad20-6a87-11e8-a2d7-55408a7195d1"

Note: Replace the id values in the previous commands with those noted in Step 3.

Issue the command from Step 3 again to confirm that there are no records present.

Start the vrm upgrade again in the SDDC Manager UI.

Note: This time vrm upgrade will not attempt to update NTP on Log insight as there are no records in the table.

Once the upgrade is successful, issue commands similar to the following to repopulate the loginsight table in the cassandra database with the smae data removed in Step 5:

/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "insert into loginsight(id,createddate,dalversion,enhancedloggingenabled,hostname, ipaddress,modifieddate,name,scope,vipaddress,vipfqdn,vmsize) values (87748610-6a87-11e8-a2d7-55408a7195d1, '2018-06-07 22:56:33+0000', '1',True,'loginsight-vm-1.vcf.corp.local', '192.x.x.x', '2018-06-07 22:56:33+0000', 'loginsight-vm-1','public','192.168.16.18','loginsight-cluster.vcf.corp.local','sxmall')"
/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "insert into loginsight(id,createddate,dalversion,enhancedloggingenabled,hostname,ipaddress,modifieddate,name,scope,vmsize) values (8774ad21-6a87-11e8-a2d7-55408a7195d1, '2018-06-07 22:56:33+0000', '1',True,'loginsight-vm-2.vcf.corp.local', '192.x.x.x', '2018-06-07 22:56:33+0000', 'loginsight-vm-1','public','sxmall')"
/opt/vmware/cassandra/apache-cassandra-2.2.4/bin/cqlsh -e "insert into loginsight(id,createddate,dalversion,enhancedloggingenabled,hostname,ipaddress,modifieddate,name,scope,vmsize) values (87748610-6a87-11e8-a2d7-55408a7195d1, '2018-06-07 22:56:33+0000', '1',True,'loginsight-vm-1.vcf.corp.local', '192.x.x.x', '2018-06-07 22:56:33+0000', 'loginsight-vm-1','public','sxmall')"

Note: Replace the environment-specific values (names, IP addresses, sizes, dates, etc...) with the values saved in Step 4.

Related Information

To be alerted when this article is updated, click the Subscribe to Article link in the Actions box.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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

VMware Cloud Foundation 2.2.x

Take Our Survey

Support Assistant