Pivotal Knowledge Base

Follow

PCF Runtime for Windows install fails with error: "Failed compiling packages > xxx : Timed out pinging to xxx after 600 seconds"

Environment 

Pivotal Cloud Foundry (PCF) 1.9-11
PCF Runtime for Windows 1.9-11
vSphere Stemcell

Overview

In this example, we will provide guidance for troubleshooting install issues for PCF Runtime for Windows using a manually built stemcell for vsphere. 

  1. Install-CFFeatures fails
  2. Administrator: Windows PowerShell security warning
  3. Invalid configuration for device '5'
  4. Windows VM IP not assigned 

Symptom

When attempting to install PCF Runtime for Windows, you get the following error during apply changes:

Deploying
---------

Director task 11868
  Started preparing deployment > Preparing deployment. Done (00:00:00)

  Started preparing package compilation > Finding packages to compile. Done (00:00:00)

  Started compiling packages
  Started compiling packages > golang1.7-windows/f257da9d21d9394c88ad0fdc130f1c9f0c93f862
  Started compiling packages > go-windows/d185f9c70652052c8a1a09a2f3ff9969510f4fda
  Started compiling packages > garden-windows/6978fe77048f4c83ec5f72c7fcf518e942278f08
  Started compiling packages > golang-windows/b50a5aa7e459bb5ff6a366e30e44f22b340d61fb
   Failed compiling packages > golang1.7-windows/f257da9d21d9394c88ad0fdc130f1c9f0c93f862: Timed out pinging to daf6ae58-aaab-4568-b19e-7425b054c457 after 600 seconds (00:10:34)
   Failed compiling packages > go-windows/d185f9c70652052c8a1a09a2f3ff9969510f4fda: Timed out pinging to 4d455861-629a-4209-ad77-8e297068a61f after 600 seconds (00:12:00)
   Failed compiling packages > golang-windows/b50a5aa7e459bb5ff6a366e30e44f22b340d61fb: Timed out pinging to 741adaf1-64a9-4540-ad74-ede58a4178f3 after 600 seconds (00:12:08)
   Failed compiling packages > garden-windows/6978fe77048f4c83ec5f72c7fcf518e942278f08: Timed out pinging to f383e010-c81d-4c09-bf0b-25e65f458b53 after 600 seconds (00:12:18)

Error 450002: Timed out pinging to daf6ae58-aaab-4568-b19e-7425b054c457 after 600 seconds

Task 11868 error

For a more detailed error report, run: bosh task 11868 --debug
===== 2017-06-29 13:23:04 UTC Finished "bundle exec bosh -n deploy"; Duration: 741s; Exit Status: 1
{"type": "step_finished", "id": "bosh.deploying.p-windows-runtime-debcc6764bb2f7b91e97"}
Exited with 1.

Cause 

Most of the issues occur due to either incorrectly following the procedure (misinterpreted steps) or issues with the procedure for building a Windows stemcell for vSphere. The incorrectly built stemcell causes the Windows VM not to boot up properly therefore the Bosh agent on the VM cannot communicate with the Bosh director and hence the timeout is reached.

Resolution

Follow the steps to resolve these issues:

Note: Reference the following procedure for mentioned steps - https://docs.pivotal.io/pivotalcf/1-9/windows/vsphere-stemcell-build.html

  1. Install-CFFeatures fails - When following Step 2 (Download BOSH PSModules), you need to download the bosh-psmodules.zip from the github link. If you try build the BOSH PSModules from the source, the PowerShell Install-CFFeatures will fail with the following: 
    The 'Install-CFFeatures' command was found in the module BOSH.CFCELL, but the module could not be loaded.
  2. Administrator: Windows PowerShell security warning - Open vSphere client and connect to the console of the Windows VM that failed to boot up, confirm you see the following error:
    Security Warning
    Run only scripts that you trust. While scripts from the
    Internet can be useful, this script can potentially harm your computer. Do you want to run
    C:\ProgramFiles\WindowsPowerShell\Modules\BOSH.Utils\BOSH.Utils.psm1?
    [D] Do not run  [R] Run once  [S] Suspend [?] Help (default is "D"):
    The default Windows permissions doesn't allow 3rd party PowerShell modules. The solution is to add an extra entry into BOSH.Sysprep.psm1 to bypass the execution policy. Before running Step 7, (Sysprep and apply security policies) edit the following:
    In the BOSH.Sysprep/BOSH.Sysprep.psm1 file in the module you put into C:\Program Files\WindowsPowerShell\Modules, change the line below and add -ExecutionPolicy Bypass.
    Before:
    C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Command Disable-AutomaticUpdates
    After (Edited):
    C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -Command Disable-AutomaticUpdates
    Note: There are 3 instances of this line and all 3 should be changed.

  3. Invalid configuration for device '5' - Open vSphere client and connect to the console of the Windows VM that failed to boot up, confirm you see the following error:
    Invalid configuration for device '5'
    This error will occur if you don't De-select Connect CD/DVD Drive which is one of the last parts of Step 1 (Create base VM for stemcell). To resolve this you need to rebuild your stemcell from Step 1 of the procedure and confirm you have de-selected the CD/DVD drive.

  4. Windows VM IP not assigned - Windows assigns its own IP if the Bosh agent is not installed correctly on the VM before converting to OVA. The resolution is to redo Step 5 (Download and Install the BOSH Agent) of the procedure as it is not very clear. Below are the steps needed to correctly install Bosh agent on the VM during the stemcell build process.
    1. Download agent.zip file.
    2. Transfer the agent.zip file you downloaded from the releases page to your Windows VM.
    3. Place the agent.zip file in the C:\Windows directory
    4. Open PowerShell and cd to the Windows directory and run the following:
      Install-Agent -IaaS vSphere -agentZipPath agent.zip

Verify the agent Install completes successfully.

Comments

Powered by Zendesk