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

Pod creation in new K8S Namespaces is stuck at “ContainerCreating” state in PKS (76363)

Last Updated: 10/27/2020Categories: TroubleshootingTotal Views: 2798Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Pod creation in new namespaces is stuck at ContainterCreating state, however the existing namespaces are running fine.

When you inspect NSX-T Manager, you do not see any logical switch created for the new namespace.

The /var/vcap/sys/log/ncp/ncp.stdout.log on Master nodes shows NSX IP block is exhausted however you have sufficient free subnets in the Pod IP block.
1 2019-11-13T13:19:57.320Z c32251ce-acb9-471c-920c-a5981a54da07 NSX 11354 - [nsx@6876 comp="nsx-container-ncp" subcomp="ncp" level="ERROR" errorCode="NCP00025"] nsx_ujo.ncp.nsx.manager.nsxapi create_logical_switch failed, cause: NSX IP block exhausted, args: (u'pks-52835768-e529-4393-b1a5-47883bc904dc-tpikna-yelb-0', False, [{'scope': n[truncated] kwargs: {}

Cause

This issue occurs if you have updated the PKS cluster with a Network profile which does not have the parameter pod_subnet_prefix.
pks update cluster <cluster-name> --network-profile <network-profile-name>

During the update-cluster operation, pks uses the network profile contents that are being updated and not using the defaults from the original cluster manifest. So if the pod_subnet_prefix value is missing in the profile, then it resets this value to 0 which causes the logical switch creation failure.

When you use the update-cluster operation with network profile, ensure to include the below parameters in the network profile.
"t0_router_id": "to router_id",
"fip_pool_ids": ["floating_ip_pool_id"],
"pod_ip_block_ids": ["pod_ip_block_id",”pod_ip_block_id”],
"pod_subnet_prefix": prefix_size,   #default 24
"single_tier_topology": false

Resolution

This is a known issue when you update the PKS cluster with a network profile and will be fixed in coming versions of PKS 1.6.x.

Workaround

To work around this issue, update the subnet_prefix size in PKS cluster manifest file and then update the cluster with new network profile which includes the required parameters.

Export the cluster manifest file from bosh by running the command:
bosh manifest -d deployment_service_instance_name >& manifest.yml

Edit the manifest file, search for the below fields and replace them with correct values. There will be 2 places where these fields have to be changed.
single_tier_topology:
subnet_prefix:
tier0_router:

Update the cluster config with latest manifest file by running the command:
bosh deploy -d <deployment_name> manifest.yml

Namespace logical switch will be created after this and pod creation should be successful.

Now update the cluster again with new network profile including all the necessary parameters in network profile so that Bosh will be synced with cluster info.

Create a new network profile by including below parameters in addition to current parameters. For more information on network profile definition and creation, see Using Network Profiles in PKS documentation.

"t0_router_id": "to router_id",
"fip_pool_ids": ["floating_ip_pool_id"],
"pod_ip_block_ids": ["pod_ip_block_id",”pod_ip_block_id”],
"pod_subnet_prefix": prefix_size,   #default 24
"single_tier_topology": false

Update the cluster with new profile by running:

pks update-cluster <cluster-name> --network-profile <new-network-profile-name>

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Application Remote Collector 在重新引导后自动从 7.5 升级到 8.0 (76412)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

Take Our Survey

Support Assistant