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

PKS cluster creation fails with "Error: Timed out sending ‘get_state’ to worker node after 45 seconds" (67420)

Last Updated: 3/14/2019Categories: TroubleshootingTotal Views: 3704Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

PKS cluster creation is failing with Error: Timed out sending ‘get_state’ to worker node after 45 seconds.

You see that Master and Worker nodes are created and all the processes are running fine.

You are using 172.17.x.x/36 or one of the PKS Reserved subnet for PKS Management plane.

When you run Bosh task xxx for cluster cluster creation, you see the output similar to:

Task 204 | 18:08:12 | Preparing deployment: Preparing deployment
Task 204 | 18:08:14 | Warning: DNS address not available for the link provider instance: pivotal-container-s-ab25c4850e38
Task 204 | 18:08:14 | Warning: DNS address not available for the link provider instance: pivotal-container-s0-ab25c4850e38
Task 204 | 18:08:14 | Warning: DNS address not available for the link provider instance: pivotal-container-s-ab25c4850e38
Task 204 | 18:08:26 | Preparing deployment: Preparing deployment (00:00:14)
Task 204 | 18:08:33 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 204 | 18:08:33 | Creating missing vms: master/33c9b266-30e7-4f0f-9bd1-f51e2aed9577 (0)
Task 204 | 18:08:33 | Creating missing vms: worker/898c20e9-5962-415e-90ca-0e1e32bb662f (0)
Task 204 | 18:09:40 | Creating missing vms: master/33c9b266-30e7-4f0f-9bd1-f51e2aed9577 (0) (00:01:07)
Task 204 | 18:09:46 | Creating missing vms: worker/898c20e9-5962-415e-90ca-0e1e32bb662f (0) (00:01:13)
Task 204 | 18:09:47 | Updating instance master: master/33c9b266-30e7-4f0f-9bd1-f51e2aed9577 (0) (canary)(00:02:19)
Task 204 | 18:12:06 | Updating instance worker: worker/898c20e9-5962-415e-90ca-0e1e32bb662f (0) (canary)(00:05:09)
L Error: Timed out sending ‘get_state’ to 040fdd68-b97f-46e6-ad69-93e2bc598380 after 45 seconds
Task 204 | 18:17:15 | Error: Timed out sending ‘get_state’ to 040fdd68-b97f-46e6-ad69-93e2bc598380 after 45 seconds

Cause

This issue occurs when your PKS Management plane subnet conflicts with the Reserved IP Blocks.This restriction applies to all virtual machines (VMs) deployed during the PKS installation process, including the PKS control plane, Ops Manager, BOSH Director, and Harbor Registry. If you use them already, then Kubernetes worker nodes cannot reach Harbor or internal Kubernetes services and cluster creation will fail.

Resolution

Ensure to not to use the below Reserved Subnets any where in your PKS environment. If you use them already, you need to re-deploy the PKS environment by choosing the proper subnets. For more information, see Plan IP Blocks section under Planning, Preparing, and Configuring NSX-T for PKS.

The Docker daemon on the Kubernetes worker node uses the subnet in the following CIDR range. Do not use IP addresses in the following CIDR range:

172.17.0.1/16

172.18.0.1/16

172.19.0.1/16

172.20.0.1/16

172.21.0.1/16

172.22.0.1/16

If PKS is deployed with Harbor, Harbor uses the following CIDR ranges for its internal Docker bridges. Do not use IP addresses in the following CIDR range:

172.18.0.0/16

172.19.0.0/16

172.20.0.0/16

172.21.0.0/16

172.22.0.0/16

Each Kubernetes cluster uses the following subnet for Kubernetes services. Do not use the following IP block for the Nodes IP Block:

10.100.200.0/24

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

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:

VMware PKS 1.x

Take Our Survey

Support Assistant