DevTest VSE Pod Configuration Error and Orphaned Resource Resolution in OCP

Products

• Service Virtualization

Issue/Introduction

In OCP environment, we are experiencing an issue where the VSE pod vse1 is displaying a create container config error and cannot be redeployed. This problem occurred from accidentally deleting the vse1 pod and subsequently deploying a new pod, vse-01, using a Harness deployment, which has likely led to a naming convention conflict and orphaned resources. Our goal is to resolve this configuration error, successfully recreate vse1, and delete vse-01.

Environment

DevTest 10.9.0 Images in OCP environment

Cause

Deleting a **StatefulSet** in Kubernetes/OpenShift does not automatically remove all associated resources, such as headless Services or pods that are already in a specific lifecycle state. If a deployment is recreated with conflicting names or via different deployment tools (e.g., Harness vs. Helm) before the original objects are fully purged, the cluster may retain orphaned pods in an 'orphaned' or 'orphaned-but-running' state.

Resolution

The orphaned objects were cleared by deleting the StatefulSet without terminating active pods.

1. 1. Deleted the problematic StatefulSet: kubectl delete statefulsets <name> -n <namespace>.
   2. Cleaned up the orphaned state.
   3. Redeployed the VSE pods using Helm install, successfully recreating vse1 and removing the accidental vse-01 deployment.

 

 

 

 

 

Additional Information

https://techdocs.broadcom.com/us/en/ca-enterprise-software/devops/devtest-solutions/10-9/installing/installing-devtest-with-container-platforms/configure-and-deploy-devtest-using-helm-chart/deploy-using-helm-chart.html