cloudfoundry / bosh-azure-cpi-release

BOSH Azure CPI
Apache License 2.0
63 stars 88 forks source link

Error on bosh create-env command run on Azure #461

Closed jitendrs closed 6 years ago

jitendrs commented 6 years ago

--------------------MESSAGE FROM ADMIN, DELETE BEFORE SUBMITTING----------------------

Hi Folks, I am getting below error while executing Bosh create-env on Azure.

CPI Version: 35.2.0 BOSH Version: 5.0.1-2432e5e9-2018-07-18T21:41:06Z CF Version: Diego Version:

Stemcell

Version: Distro:

Environment

### Issue Details

creating stemcell (bosh-azure-hyperv-ubuntu-trusty-go_agent 3586.24): CPI 'create_stemcell' method responded with error: CmdError{"type":"Unknown","message":"undefined method `[]' for nil:NilClass","ok_to_retry":false}

Command with exxecution details:- jumpbox@cfboshlod01:~$ bosh create-env bosh.yml --state=state.json --vars-store=creds.yml -o cpi.yml -v director_name=AZBoshDirector -v internal_cidr=172.16.4.0/24 -v internal_gw=172.16.4.1 -v internal_ip=172.16.4.6 -v vnet_name=cfazvnse -v subnet_name=cfazpubsub01 -v subscription_id=XXX -v tenant_id=XXX -v client_id=XXX-v client_secret=XX -v resource_group_name=AZ-CF-POC -v storage_account_name=cfazgpsse -v default_security_group=XX Deployment manifest: '/home/jumpbox/bosh.yml' Deployment state: 'state.json'

Starting registry... Finished (00:00:00) Uploading stemcell 'bosh-azure-hyperv-ubuntu-trusty-go_agent/3586.24'... Failed (00:00:01) Stopping registry... Finished (00:00:00) Cleaning up rendered CPI jobs... Finished (00:00:00)

creating stemcell (bosh-azure-hyperv-ubuntu-trusty-go_agent 3586.24): CPI 'create_stemcell' method responded with error: CmdError{"type":"Unknown","message":"undefined method `[]' for nil:NilClass","ok_to_retry":false}

bingosummer commented 6 years ago

Could you please check whether the containers bosh and stemcell exist in your storage account cfazgpsse?

bingosummer commented 6 years ago

@jitendrs Are you still hitting the issue? If not, I would like to close it.

jitendrs commented 6 years ago

Hey @bingosummer issue got resolved. The issue was related to permission on storage account for Azure. thanks for response mate.