search

vmware / script-runtime-service-for-vsphere

The Repository contains Script Runtime Service for vSphere. A service for managing server-side PowerCLI instances to run commands and scripts against VCenter servers.
Other
34 stars 7 forks source link

vCenter client plug-in install hangs #84

Open AndrewThor9 opened 11 months ago

AndrewThor9 commented 11 months ago

Describe the bug

Hi, I'm running into an issue while deploying the appliance that the plug-in is not getting installed on the vCenter, the task hangs at 0%. I see in the appliance log (power-actions-setup.log) that it is waiting for it to be installed so it seems to be a vCenter issue. I'm logged in with the default administrator account. vCenter version: 7.0 U3o (22357613). I have doubt that it matters but the solution is on the same network, no firewall between the appliance and the vCenter. The vCenter has self-signed certificate but I used the checkbox to disable certificate check upon deployment. Any pointers where to check why it doesn't want to be installed on the VC? Or is there any other dependency which I'm missing before I could deploy it? Thank you in advance!

Reproduction steps

  1. Downloaded the latest OVA (VMware-Power-Actions-1.0.3.0-22361595_OVF10.ova)
  2. Deployment through the UI with the proper parameters (VM name, target cluster and datastore, port group, credentials (using the given example P@ssword123! to ensure service startup), IP and DNS).

Expected behavior

Plug-in installed and available on the vCenter UI.

Additional context

I have noticed one relevant warning on the console during deployment: image "vCenter address does not match its certificate common name . This may prevent plug-in from registering into the vCenter" This is due to the self-signed certificate? I don't know others, but in many cases, I use VC like this and PowerActions would be a great help if it would work natively without any modification to the VC certificate - if that's the issue at all.

kamennikolov commented 11 months ago

It seems like the certificate common name is by FQDN and during the installation you entered the IP address, instead of the FQDN for vCenter server address. Please try re-installing by specifying the FQDN instead of the IP address.