Unable to redeploy VIDB reusing the same IP after deleting VIDB from second VCF instance

Products

• VCF Operations

Issue/Introduction

In VCF Operations, the VCF Identity Broker (VIDB) was removed from the second VCF Instance using the delete_vidb.py script from Deletion of Identity Broker from VCF Operations 9.1, the IP that was used is not able to be re-used when re-deploying a new VIDB instance. The IP that was used is still actively pinging.

Environment

VCF Operations 9.1.0

Cause

The delete_vidb.py script failed to remove the VIDB pods from the VCF services runtime cluster in the second VCF instance.

Resolution

Validate that the VIDB pods are still present

1. Log in to VCF Operations and navigate to Build > Lifecycle > Fleet Management > Components
2. Click the VCF services runtime component in the second VCF instance
3. Scroll down to the list of nodes and identify the IP for a control plane node
4. Log in to the control plane IP identified in step 3 as vmware-system-user via SSH
5. Switch to the root user

   sudo -i

6. List the pods in the vidb-external namespace

   kubectl get pods -n vidb-external

If the pods are still running, Contact Broadcom Support and mention this KB article for additional support