'Expected non-empty Director URL.' Error when using bosh commands.
search cancel

'Expected non-empty Director URL.' Error when using bosh commands.

book

Article ID: 408349

calendar_today

Updated On:

Products

VMware Tanzu Platform - Cloud Foundry VMware Tanzu Application Service VMware Tanzu Application Platform

Issue/Introduction

You are trying to enter bosh commands (such as 'bosh vms') into your terminal and see the following error output:

~$ bosh vms
Using environment '10.0.x.x' as client 'ops_manager'

Expected non-empty Director URL. 
Exit code 1

Cause

You do not have proper bosh-cli credentials configured locally to reach the bosh Director.

Resolution

Configure proper credential for your desired bosh director session by following the steps below (in-order). 

1.) Log into desired OpsManager GUI

2.) Select / Click on Bosh tile.

3.) Select 'Credentials' Tab, then select 'Bosh CommandLine Credentials'.

4.) When you select "Link to Credential" above, you will see the actual credential appear on the screen. Copy the data field from this output, as the example shows below:

# Actual Output:
{"credential":"BOSH_CLIENT=ops_manager BOSH_CLIENT_SECRET=xxxxxxxxxxxxxx BOSH_CA_CERT=/var/tempest/workspaces/default/root_ca_certificate BOSH_ENVIRONMENT=10.0.0.10 bosh "}

# Copy the data field of above output:
BOSH_CLIENT=ops_manager BOSH_CLIENT_SECRET=xxxxxxxxxxxxxx BOSH_CA_CERT=/var/tempest/workspaces/default/root_ca_certificate BOSH_ENVIRONMENT=10.0.0.10 bosh

5.) Paste the above 'data feild' contents into your terminal session and click enter. 

6.) Try your original bosh command again, in our example the origianal command was 'bosh vms'. You should see the desired output:

~$ bosh vms
Using environment '10.0.x.x' as client 'ops_manager'

Task 668
Task 667
Task 668 done

Task 667 done

Deployment 'cf-delpoyment-xxxxx'

...

 * If this does not work, reach out to TANZU Support by Broadcom.