Pivotal Knowledge Base

Follow

Failure when deploying Ops Manager Director

Environment 

Product Version
Pivotal Cloud Foundry® (PCF) 1.7.x+
Component Ops Manager Director

Symptom

The Ops Manager Director fails to deploy with an error message which looks like the following example:

Command 'deploy' failed:
Deploying:
Creating instance 'bosh/0':
Creating VM:
Creating vm with stemcell cid 'ami-269cb445 light':
CPI 'create_vm' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":"Cannot delete settings for 'i-fb680654', got HTTP 403","ok_to_retry":false}
===== 2016-07-25 06:04:06 UTC Finished "bosh-init deploy /var/tempest/workspaces/default/deployments/bosh.yml"; Duration: 56s; Exit Status: 1
{"type": "step_finished", "id": "bosh_product.deploying"}
Exited with 1.

If you look at the IaaS level during deployment, a VM for the Director gets spawned and terminated, which means the system is able to talk to your IaaS API without any problem. 

Cause

This is caused by HTTP proxy settings that you can configure in the Ops Manager as described in Configuring Proxy Settings for BOSH CPI

If you did not include 127.0.0.1 and the Ops Manager Director (or Bosh Director's) IP address in No Proxy field, HTTP requests to 127.0.0.1, which Ops Manager does while deploying Ops Manager Director, will go to the proxy server, which most likely ends up returning an error. 

Note that in the example above, the error was HTTP 403, but it may vary depending on your proxy server.  

Resolution 

  • The No Proxy setting needs to be updated so that it includes 127.0.0.1 as well as the IP address of the Ops Manager Director. 
  • In version 1.7.x, the Ops Manager web UI does not provide a page to change the proxy settings after the initial setup is done. Contact Pivotal Support if you need to change the No Proxy setting in a running Ops Manager. 

 

Comments

Powered by Zendesk