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

Unable to Push apps/NCP restarting due to "Failed to initialize container orchestrator adaptor: 'external_id'" (77203)

Last Updated: 3/10/2020Categories: TroubleshootingTotal Views: 5364Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Symptoms will include all of the following:

NCP is unable to push Apps.

NCP will report restarting due to "Failed to initialize container orchestrator adaptor: 'external_id'".

NCP Log will contain events similar to the following in ./ncp/ncp.stdout.log:

./ncp/ncp.stdout.log.1:1 2020-02-09T21:41:24.287Z 7d6c57b9-e0e5-4f66-8683-c57c63241782 NSX 16223 - [nsx@6876 comp=“nsx-container-ncp” subcomp=“ncp” level=“CRITICAL”] nsx_ujo.ncp.main Failed to initialize container orchestrator adaptor: ‘external_id’ ./ncp/ncp.stdout.log.1:1 2020-02-09T21:42:26.037Z 7d6c57b9-e0e5-4f66-8683-c57c63241782 NSX 16447 - [nsx@6876 comp=“nsx-container-ncp” subcomp=“ncp” level=“CRITICAL”] nsx_ujo.ncp.main Failed to initialize container orchestrator adaptor: ‘external_id’ ./ncp/ncp.stdout.log.1:1 2020-02-09T21:43:27.073Z 7d6c57b9-e0e5-4f66-8683-c57c63241782 NSX 16673 - [nsx@6876 comp=“nsx-container-ncp” subcomp=“ncp” level=“CRITICAL”] nsx_ujo.ncp.main Failed to initialize container orchestrator adaptor: ‘external_id’

Purpose

To confirm the external_id parameter is missing:

1. Collect the list of Container Cluster(s) from NSX-T Manager:

root@NSXManager:~# curl -k -u admin -H "Content-Type: application/json" -X GET https://localhost/api/v1/fabric/container-clusters/
Enter host password for user 'admin':
{
"results" : [ {
"external_id" : "c9ef8d33-6f13-5245-b0e5-6050028bfacf",
"cluster_type" : "PAS",
"infrastructure" : {
"infra_type" : "vSphere"
},
"origin_properties" : [ ],
"resource_type" : "ContainerCluster",
"display_name" : "TEST",
"_last_sync_time" : 1580396792638
} ],
"result_count" : 1,
"sort_by" : "display_name",
"sort_ascending" : true
}

2. Verify the external_id parameter is missing for the collected Container Cluster external_id:
curl -k -u admin -H "Content-Type: application/json" -X GET https://localhost/api/v1/fabric/container-applications?container_cluster_id=c9ef8d33-6f13-5245-b0e5-6050028bfacf

Enter host password for user 'admin':
- notice here that the external_id parameter is missing in the response:

{

"results" : [ {

"container_cluster_id" : "c9ef8d33-6f13-5245-b0e5-6050028bfacf",

"container_project_id" : "b04095af-afb5-427f-b391-f86eb561a81c",

"origin_properties" : [ ],

"resource_type" : "ContainerApplication",

"_last_sync_time" : 0

}

Cause

The issue occurs when the Container Application Instance object is received by the MP Inventory, but the associated App has not yet been received. NCP creates the App without the required “external_id” field. The App fails without that field.

Resolution

This issue is resolved if running a fresh install of NSX-T 2.5.1.

If upgrading from NSX-T 2.5.0 to NSX-T 2.5.1 the below steps need to be performed as well.

After the update to NSX-T 2.5.1
-Stop all NCP instances.

Option (1) Remove only those container_cluster entries with invalid container-application entries.
Identify the impacted cluster id's with the following API calls.
(a) GET https://<NSX Manager IP>/api/v1/fabric/container-clusters/

For each item in the result of (a), do
(b) GET https://<NSX Manager IP>/api/v1/fabric/container-applications?container_cluster_id=<container_cluster_id>
(c) Check if any container-application entry without external_id in the result of (b)

If so remove the cluster id entries that are missing the external id field with the following API call.
(a) DELETE https://<NSX Manager IP>/ api/v1/fabric/container-clusters/<container_cluster_id>

Option (2) Remove all container_cluster entries.
Identify all the cluster id's with the following API calls.
(a) GET https://<NSX Manager IP>/api/v1/fabric/container-clusters/
For each item in the result of (a), use the following API call to remove.
(b) DELETE https://<NSX Manager IP>/api/v1/fabric/container-clusters/<container_cluster_id>

- Start all NCP instances

At this time if the steps in the workaround section have been applied. Those changes to the NCP.ini can be undone.

Workaround

This workaround removes the “external_id” requirement by disabling the inventory feature.

(1) login to each diego_database, for example (from OpsMgr)
bosh ssh -d <deployment-id> diego-database/xxxxxxxx
(2) sudo su
(3) cd /var/vcap/data/jobs/ncp/yyyyyyyy/config/
where yyyyyyyy should be the latest deployment ID
(4) vi ncp.ini
under [nsx_v3] section, add
enable_inventory = False                      <-- as shown, with a captial 'F' in False
(5) restart NCP
# monit restart ncp

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Intel プロセッサにおける Load Value Injection (CVE-2020-0551) の投機的実行の脆弱性に対する VMware の対応 (78194)

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

KB
•
如果存在不可靠路径，则设备中某些路径上的 I/O 可能会失败或者数据存储创建失败 (78200)

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 NSX Data Center for vSphere

Related Versions:

Take Our Survey

Support Assistant