I have installed VA in the Azure environment, but when I try to create source I cant see my cluster

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi. Can someone please help here. I have installed VA in the Azure environment, but when I try to create source I cant see my cluster

2

Hi @ameeeetster

Welcome to SailPoint developer community.

You need to create the cluster and add the VA There in the cluster. Look at this document for more information.

Thanks
Krish

3

If you have created the Cluster and VA in ISC and it’s showing as connected, you need to wait for some time to allow the VA to update itself.
If after that time it still is not selectable in the Source, you may need to restart the cluster from ISC.
We had the same issue here a few weeks ago, and it was solved by restarting the cluster from the UI.

4

@ameeeetster try to create two va and wait for update to get completed.
You will see the VA

thanks
Shantanu

5

I have done that already. Even re-created it, and then waited for almost 6 hours

6

I waited for almost 6 hours after creating the cluster, even re-created it, and that even didn’t help. I restarted the cluster as well. I got 1 VA in the cluster by the way

7

I got one VA in the cluster , but that shouldn’t be a problem, i think

9

Hey Amit, i had the same issue and it was Firewall, the Va agent was unable to complete with Charon the Va setup. So it keeps hanging the “update”.

Use the stunt script to find any obvious blockage. But once i’ve clear my promox to all the requested rules it worked very well.

best!

10

take a look at the results of the api call /beta/managed-clusters (GET)
your cluster is likely not in an operational state, which usually means issues setting the publicKey.

as others have mentioned, try deleting the cluster and re-pairing the VA to the new cluster.

if you do not see “operational”: true, you can not pair sources to this cluster

11

Hi Stephen,
you were correct. It was not in operational state. I tried deleting and recreating the cluster several times but its still the same

12

Is almost certain that it could be a comunication issue.
Try to open the Va for the internet and see if it solves.

13

Amit please also make sure that your keyPassphrase meets these requirements as well: The keyPassphrase cannot start with a special character, and cannot include !, /, \, or spaces.

I have seen issues like this cause communication issues as well as the VA is not able to connect to the tenant because of a bad keyPassphrase

Deploying Virtual Appliances - SailPoint Identity Services

14

Hi @ameeeetster
I had faced the same issue so once i setup one more va it got operational.Dont know if its a bug i got the issue in demo tenant .if you are doing for client then sailpoint support can help here.

Thanks
Shantanu

15

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.