PAS fails to deploy while running the Notification Errand

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Symptoms:
In addition to the failed errand, the following stack trace will appear on the diego_database instance in /var/vcap/sys/log/ncp/ncp.stderr.log:

Traceback (most recent call last):
  File "/usr/local/bin/ncp", line 10, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/dist-packages/nsx_ujo/cmd/ncp.py", line 16, in main
    ncp_main.start_ncp(coe)
  File "/usr/local/lib/python2.7/dist-packages/nsx_ujo/ncp/main.py", line 124, in start_ncp
    cache.CoeNSXMapping().initialize_cache()
  File "/usr/local/lib/python2.7/dist-packages/nsx_ujo/ncp/nsx/cache.py", line 1270, in initialize_cache
    self._populate_logical_routers(logical_routers)
  File "/usr/local/lib/python2.7/dist-packages/nsx_ujo/ncp/nsx/cache.py", line 288, in _populate_logical_routers
    project_key = tags[self._adaptor.get_project_tag_scope()]
KeyError: 'ncp/cf_org_guid'

Environment

Cause

The ncp daemon does not expect the T0 router to have the ncp/cluster tag and crashes.

The ncp/cluster tag may have been mistakenly added to the T0 Router when following these instructions, using an NSX-T manager newer than version 2.1, and not recognizing that the tag and scope columns had been swapped.

Resolution

From the NSX-T Manager, delete the ncp/cluster tag from the T0 Router. Redeploy PAS by clicking "Apply Changes" from the Operations (Ops) Manager interface.

Note: Do NOT delete the tag from the T1 routers; it's appropriate for T1 Routers created by the ncp daemon to have the tag, ncp/cluster.