Opsman "Unable to contact the BOSH Director when constructing certificate topology" but BOSH is running

Products

• Operations Manager

Issue/Introduction

Your BOSH director is up and running, but you see the below error when viewing the Certificates tab in Opsman:

Unable to retrieve certificates: Unable to contact the BOSH Director when constructing certificate topology

In /var/log/opsmanager/production.log on Opsman, you see BoshExecutor fails to run bosh variables on a deployment (exit_code=1) and the request fails with a 503 error

Example request:

I, [2025-05-20T12:32:07.344100 #1334255]  INFO -- : [########-####-####-####-############] Started GET "/certificates" for #.#.#.# at 2025-05-20 12:32:07 +0000
I, [2025-05-20T12:32:07.446097 #1334255]  INFO -- : [########-####-####-####-############] Processing by CertificatesController#index as HTML
.I, [2025-05-20T12:32:24.012258 #1334255]  INFO -- : [########-####-####-####-############] BoshExecutor start cmd=/usr/local/bin/bosh --no-color --non-interactive --tty --environment=#.#.#.# --deployment=p-isolation-segment-##### variables --json; pwd=/home/tempest-web/tempest/web
I, [2025-05-20T12:32:24.104280 #1334255]  INFO -- : [########-####-####-####-############] BoshExecutor stop  cmd=/usr/local/bin/bosh --no-color --non-interactive --tty --environment=#.#.#.# --deployment=p-isolation-segment-##### variables --json; pwd=/home/tempest-web/tempest/web exit_code=1
I, [2025-05-20T12:32:24.112370 #1334255]  INFO -- : [########-####-####-####-############]   Rendered layout layouts/application.html.haml (Duration: 7.2ms | Allocations: 2540)
I, [2025-05-20T12:32:24.113383 #1334255]  INFO -- : [########-####-####-####-############] Completed 503 Service Unavailable in 16567ms (Views: 7.5ms | ActiveRecord: 8246.7ms | Allocations: 22551000)

 

If you try to run the bosh variables command yourself, you get a 404 error (deployment doesn't exist):

ubuntu@opsmanager-3-0:~$ bosh -d p-isolation-segment-##### variables
Using environment '#.#.#.#' as client 'ops_manager'

Using deployment 'p-isolation-segment-#####'

Error fetching variables for deployment 'p-isolation-segment-#####':
  Director responded with non-successful status code '404' response '{"code":70000,"description":"Deployment 'p-isolation-segment-#####' doesn't exist"}'

Exit code 1

Cause

This issue can happen if you deployed a product via Opsman and the deployment gets deleted outside of Opsman, such as with the bosh delete-deployment command. Opsman thinks it is still deployed and then fails to get the variables for the certificate topology because it doesn't exist anymore.

Resolution

To resolve you need to uninstall the product or redeploy it via Opsman. Below are two ways to resolve the issue:

You only need to do one of these options

• Apply Changes to the tile in Opsman - this will recreate the missing deployment
• Delete the tile on the Opsman installation dashboard, then apply changes to it to finish uninstalling the tile - this will uninstall the product