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

Deploying VCH to cluster nested inside folders results in the Portlayer failing with message FATAL configure_port_layer ERROR: Failure finding host (): no default host found" (56471)

Last Updated: 7/13/2018Categories: TroubleshootingTotal Views: 2805Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

While deploying VCH using the < vic-machine-OS create > utility on a nested cluster inside folders results in the Port layer fails with error as below or similar:

< FATAL configure_port_layer ERROR: Failure finding host (): no default host found >"
< timeout on docker API check >

======Command Output======
time="2018-04-13T14:57:13-07:00" level=info msg="Docker API endpoint check failed: failed to connect to https://00.00.00.00:2376/info: i/o timeout"
time="2018-04-13T14:57:13-07:00" level=info msg="Collecting f26795ab-4fcd-478c-89b1-c4205f4f073d vpxd.log"
time="2018-04-13T14:57:14-07:00" level=info msg="\tAPI may be slow to start - try to connect to API after a few minutes:"
time="2018-04-13T14:57:14-07:00" level=info msg="\t\tRun command: docker -H 00.00.00.00:2376 --tls info"
time="2018-04-13T14:57:14-07:00" level=info msg="\t\tIf command succeeds, VCH is started. If command fails, VCH failed to install - see documentation for troubleshooting."
time="2018-04-13T14:57:14-07:00" level=error msg="vic/cmd/vic-machine/create.(*Create).Run.func3: Create error: context deadline exceeded\nvic/cmd/vic-machine/create.(*Create).Run:741 Create\nvic/cmd/vic-machine/common.NewOperation:27 vic-machine-windows"
time="2018-04-13T14:57:14-07:00" level=error msg=--------------------
time="2018-04-13T14:57:14-07:00" level=error msg="vic-machine-windows create failed: Creating VCH exceeded time limit of 3m0s. Please increase the timeout using --timeout to accommodate for a busy vSphere target\n"
========End Output========

When connected to the VIC admin browser UI,the port-later shows the following messages:

==========00.00.00.00:2378/logs/tail/port-layer.log==========
Apr 13 2018 21:42:44.091Z FATAL configure_port_layer ERROR: Failure finding host (): no default host found
time="2018-04-13T21:42:47Z" level=info msg="Launching portlayer server pprof server on 127.0.0.1:6063"
…
…
Apr 13 2018 21:54:21.261Z FATAL configure_port_layer ERROR: Failure finding host (): no default host found
time="2018-04-13T21:54:25Z" level=info msg="Launching portlayer server pprof server on 127.0.0.1:6063"
time="2018-04-13T21:54:25Z" level=info msg="{Formatter:0xc42032fb20 Level:debug Syslog:<nil>}"

On checking the Port-Layer logs you see entries similar to :

==========/var/log/vic/port-layer.log==========
Apr 13 2018 21:54:25.677Z DEBUG GuestInfoSource: key: guestinfo.vice./vic_machine_create_options~, value: "--target=https://it-vcntr-app-01.xx.xx.xx/Campus|--name=IT000000_7000_IT-VMVCH-APP-01|--compute-resource=SE-ABC-AB-BC-03|--image-store=00_000_00|--dns-server=00.0.00.0|--dns-server=00.0.00.00|--bridge-network=VM-1234-SE-VCH|--public-network=VM-1234-VMware|--public-network-gateway=00.00.000.0|--public-network-ip=00.00.000.00|--container-network=VM-1234-Systems-Management:VM-1234-SYSMGNT|--tls-cname=it-ABCD-app-01.xx.xx.xx|--no-tlsverify=true|--debug=1", error: %!s(<nil>)
Apr 13 2018 21:54:25.677Z DEBUG op=306.1: Creating VMOMI session with thumbprint 2B:91:76:01:7B:C4:15:B9:73:AB:6A:62:90:F5:99:9B:EC:31:EA:1F
Apr 13 2018 21:54:25.978Z DEBUG Session Environment Info:
Apr 13 2018 21:54:25.978Z DEBUG op=306.1: vSphere resource cache populating...
Apr 13 2018 21:54:26.047Z DEBUG op=306.1: Cached dc: Campus
Apr 13 2018 21:54:26.177Z DEBUG op=306.1: Cached cluster: /Campus/host/TBE/vPod2/AB-BC-CD-01
Apr 13 2018 21:54:26.707Z DEBUG op=306.1: Cached ds: 02_948_30
Apr 13 2018 21:54:26.726Z DEBUG op=306.1: Cached pool: /Campus/host/TBE/vPod2/AB-BC-CD-01/Test
Apr 13 2018 21:54:26.734Z DEBUG op=306.1: Cached folders: Campus
Apr 13 2018 21:54:26.736Z DEBUG op=306.1: Error count populating vSphere cache: (1)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs when ESXI Cluster is nested within folders.

Resolution

This is a known issue affecting vSphere Integrated Containers if deployed in Nested Environments. There is currently no resolution. This issue is to be addressed in future versions of the product.

Related Information

For updates regarding this issue subscribe to this KB and look for the release notes for future release versions.

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 vSphere Integrated Containers

VMware vSphere

Related Versions:

VMware vSphere Integrated Containers 1.x

Take Our Survey

Support Assistant