Configuring Ops Manager on Azure Error, "Failed to upload page blob"

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Symptoms:

You are configuring Operations Manager deployed on Azure when you see the following error:

Command 'deploy' failed: creating stemcell (bosh-azure-hyperv-ubuntu-trusty-go_agent 3363.15): 
CPI 'create_stemcell' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":
"Failed to upload page blob: #\u003cFaraday::ConnectionFailed\u003e\n/home/tempest-web/
.bosh_init/installations/b793a6cf-6660-46a6-7b49-1bcbed73a9c5/packages/ruby_azure_cpi/lib/ruby/2.2.0/resolv-replace.rb:23:in 
`initialize'\n/home/tempest-web/.bosh_init/installations/b793a6cf-6660-46a6-7b49-1bcbed73a9c5/packages/ruby_azure_cpi/
lib/ruby/2.2.0/resolv-replace.rb:23:in `initialize'\n/home/tempest-web/.bosh_init/installations/b793a6cf-6660-46a6-7b49-1bcbed73a9c5/
packages/ruby_azure_cpi/lib/ruby/2.2.0/net/http.rb:879:in `open'\n/home/tempest-web/.bosh_init/installations/b793a6cf-6660-46a6-7b49- 
... `run'\n/home/tempest-web/.bosh_init/installations/b793a6cf-6660-46a6-7b49-1bcbed73a9c5/packages/bosh_azure_cpi/bin/azure_cpi:35:in 
`\u003cmain\u003e'","ok_to_retry":false} ===== 2017-05-26 14:04:23 UTC Finished "bosh-init deploy 
/var/tempest/workspaces/default/deployments/bosh.yml"; Duration: 410s; Exit Status: 1 {"type": "step_finished", 
"id": "bosh_product.deploying"} Exited with 1.

 

Environment

Cause

Operations Manager is able to contact management.azure.com to create the director virtual machine (VM) but, it can't store Stemcell into the storage account.

 

Resolution

Here are the troubleshooting steps to resolve this issue:

1. Check what is configured in the Operations Manager in the director tile under Azure config. Check if you have properly configured the two sets of Blobstore:

   • Blobstore for BOSH
   • Deployment Blobstore (typically 5 or more) with a similar naming sequence for storing all the VMs

   For more details on setting up these blobstores, please see here.

2. Go to the Azure portal -> storage account. Make sure:

   • Bosh storage account has 3 blob containers for Bosh, Ops Manager, and Stemcell and one table named `stemcells'

   • Deployment storage account has the same 2 containers for BOSH and Stemcell

3. Check if your endpoints to specific storage URLs have access on your firewall. You can open access to the entire .domain windows.net. If you are unable to open the entire domain then you should be able to provide access to these specific URLs:

   • <your storage>.blob.core.windows.net

   • <your storage>.queue.core.windows.net

   • <your storage>.table.core.windows.net