bosh-bootloader: Error running bosh commands after a bbl up

Hi,

This worked for me a few weeks ago. This is for AWS. I am running on OSX Sierra (10.12.6)

I did

bbl plan --iaas aws --aws-access-key-id <xxxx> --aws-secret-access-key <zzz> --aws-region us-east-1 --lb-type concourse

and then

bbl up --iaas aws --aws-access-key-id <xxxx> --aws-secret-access-key <zzz> --aws-region us-east-1 --lb-type concourse

then I could run bosh vms etc. Cleaning up: I ran a bbl destroy command, which completed successfully.

However, when I tried to run the bbl steps above again (in a new directory). It deploys without any errors. I then try to run bosh vms (or any valid bosh commands) I get the following error

Validating Director connection config:
  Parsing certificate 1: Missing PEM block

Exit code 1

I was on bbl 6.6.4. I tried updating to 6.6.7 but still no luck.

Was there something new or some extra steps I have to take?

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 15 (3 by maintainers)

Most upvoted comments

You need to quote the expression you want to evaluate for BOSH_CA_CERT to be correctly set in your environment.

eval "$(bbl --state-dir $ARA_STATE_BBL print-env)"

genevieve on May 8, 2018

20 years a Linux admin and the quotes get me!

forever grateful genevieve!

I hope this saves some other poor smuck like me.

actdiux on May 8, 2018

I just called out in the docs that the quotes are necessary: https://github.com/cloudfoundry/bosh-bootloader/blob/master/docs/howto-target-bosh-director.md

@astrieanna which error output are you talking about? It’s a little tricky because there is no bbl error, and to bosh it just looks like the BOSH_CA_CERT is bad. bosh could maybe say something when BOSH_CA_CERT is bad like Did you target this director with 'eval "$(bbl print-env)"'? Those quotes are necessary! I’m not sure if they would want to add something like that.

nwmahoney on Mar 12, 2019