Friday, May 8, 2020

Restart embedded vRealize Orchestrator on vRA8.1

I was working with a customer to set up a Powershell host. We had to configure kerberos for a powershell host and needed to restart the vco (vRealize Orchestrator) server.  It's okay to restart the vRA server but that takes a considerable amount of time.  My customer knew how to restart the pod and I thought I would share the information here.  Following are the commands to simply get vRO restarted without rebooting vRA.

You'll need to be logged into the vRA terminal prompt.  Use SSH or open a terminal window in your vCenter server.  Log in as root and continue with the following instructions.

First, we need to identify the vco name space.  Issue the following command to find it:

kubectl get pods --all-namespaces | grep vco

You'll get a result similar to this:

prelude vco-app-7946c47d8f-vq4ds ...

Once you have the results, copy the pod id.  In this case, it's vco-app-7946c47d8f-vq4ds.

You can now issue the command to delete the pod.  Kubernetes will know it needs to restart the pod if it does not exist.  Just execute the delete process like this:

kubectl delete pods -n prelude vco-app-7946c47d8f-vq4ds

You should see a message displayed indicating the pod was deleted.  The message will be similar to:

pod "vco-app-7946c47d8f-vq4ds" deleted

If you reissue the command to get all namespaces:

kubectl get pods --all-namespaces | grep vco

you will see that the vco-app is restarted.

After a couple of minutes, you can log into the Orchestrator service and continue working.

Hope this is useful.

Thanks for reading.

No comments:

Post a Comment