VMware Cloud Community
Grzesiekk
Expert
Expert
Jump to solution

vRO 8.0.1 and vCenter WebClient on VC 6.0(windows) // VCSA 6.7 appliance

Hello,

is this supposed to work, to have Orchestrator plugin running on webclint in VC 6.0 having vRO 8.0.1 ? I did as per documentation:

Configure vRealize Orchestrator Plugin for vSphere Web Client

Uploded the plugin into 8.0.1 appliance

root@vrz-p-vro001 [ /data/vco/usr/lib/vco/downloads ]# ls -l

total 15580

-rw-r--r-- 1 kube docker 8891510 Dec 11 11:03 migration-tool.zip

-rw-r--r-- 1 root root   7025307 Mar 13 09:35 vco-plugin.zip

drwxr-xr-x 6 kube docker    4096 Mar  9 16:03 vco-repo

I did run the workflow to register it

x9.png

I have rebooted the VC 6.0, and the plugin is not working in webclient Flex/Html.

I checked interoperability matrix, it says that is is supported to have 8.0.1 and vc 6.0

Any idea what i am doing wrong?

I also gave it a try on VCSA 6.7 appliance (psc+vc simple installation).

What i dont understand is why this is getting inside the plugin urlo 10.244.0.xxx , in field  when running register webclient workflow External address to advertise this Orchestrator.

x14.png

This 10.244.0.XXX is the container ip .

I tried now with https://FQDN  no ports etc. just fqdn

x15.png

Now the when i login with flex client i see a change, i see the orchestrator icon but nothing is inside

x11.png

x12.png

So i am stuck again, And this is on 6.7 VCSA appliance, not 6.0 windows.

while on VC console i can execute

wget https://vro.infralab.local/vco/vsphere-web-client/vco-plugin.zip --no-check-certificate

and plugin zip is being downloaded

Is this supposed to work with flex client  ? The plugin is not visible in html5 client at all (anyone else has it there?)

--- @blog https://grzegorzkulikowski.info
Reply
0 Kudos
1 Solution

Accepted Solutions
daphnissov
Immortal
Immortal
Jump to solution

I would be genuinely shocked if this is even supposed to work. 6.0 is now officially unsupported.

View solution in original post

Reply
0 Kudos
9 Replies
daphnissov
Immortal
Immortal
Jump to solution

I would be genuinely shocked if this is even supposed to work. 6.0 is now officially unsupported.

Reply
0 Kudos
Grzesiekk
Expert
Expert
Jump to solution

I have exactly the same behaviour on VC 6.7 Appliance. Any chance you have it working and you could paste me the result from your MOB vro extension output ? Not sure what i am doing wrong.

--- @blog https://grzegorzkulikowski.info
Reply
0 Kudos
daphnissov
Immortal
Immortal
Jump to solution

Sorry, I'm not touching vRO/vRA 8.0 with a 10-foot pole.

Reply
0 Kudos
daphnissov
Immortal
Immortal
Jump to solution

You may want to check the ownership of the file that got uploaded and ensure the permissions are correct.

Reply
0 Kudos
Grzesiekk
Expert
Expert
Jump to solution

permissions are correct, i managed to get the plugin inside but VRO server is not inside the plugin now 😕 (upaded the issue description post#0)

--- @blog https://grzegorzkulikowski.info
Reply
0 Kudos
iiliev
VMware Employee
VMware Employee
Jump to solution

If you see it in the vSphere UI, that means the plug-in has been downloaded from vRO server and deployed.

As you don't see any vRO servers in the plug-in UI, that likely means that there is some issue when the plug-in calls vRO server REST API to fetch the data. To troubleshoot this, yo need to check what is logged in vSphere Web Client UI logs (the main log file is vsphere_client_virgo.log).

BTW, as this plug-in is Flex-based, you won't see it in vSphere HTML5 client. There is another plug-in for HTML5 client, currently still in Beta.

Reply
0 Kudos
Grzesiekk
Expert
Expert
Jump to solution

Not sure, how to interpret that , apparently port is invalid ?

[2020-03-13T13:47:45.995Z] [WARN ] data-service-pool-440        70000277 100007 200002 com.vmware.vco.adapter.concurrent.VcoExecutorService              Error executing async task org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'clientHttpRequestFactory' defined in URL [bundleentry://378.fwk2035475937/META-INF/spring/bundle-context.xml]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.vco.adapter.http.SamlClientHttpRequestFactory]: Factory method 'newInstance' threw exception; nested exception is java.lang.IllegalArgumentException: Port is invalid

        at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1181)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1075)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:513)

        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)

        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:331)

        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:207)

        at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1098)

        at com.vmware.vco.session.impl.VcoServiceFactoryImpl.createRestTemplate(VcoServiceFactoryImpl.java:329)

        at com.vmware.vco.session.impl.VcoServiceFactoryImpl.access$300(VcoServiceFactoryImpl.java:44)

        at com.vmware.vco.session.impl.VcoServiceFactoryImpl$2.call(VcoServiceFactoryImpl.java:168)

        at com.vmware.vco.session.impl.VcoServiceFactoryImpl$2.call(VcoServiceFactoryImpl.java:162)

        at com.vmware.vco.adapter.concurrent.VcoExecutorService.executeAndWaitForAnyWithTimeout(VcoExecutorService.java:80)

        at com.vmware.vco.session.impl.VcoServiceFactoryImpl.createVcoServicesForConfigurations(VcoServiceFactoryImpl.java:143)

        at com.vmware.vco.session.impl.VcoServiceFactoryImpl.createVcoServices(VcoServiceFactoryImpl.java:90)

        at com.vmware.vco.session.impl.VcoServiceFactoryImpl.checkVcoServicesFor(VcoServiceFactoryImpl.java:217)

        at com.vmware.vco.session.impl.VcoSessionFactoryImpl.lookupVcoSession(VcoSessionFactoryImpl.java:247)

        at com.vmware.vco.session.impl.VcoSessionFactoryImpl.getVcoServicesForVc(VcoSessionFactoryImpl.java:228)

        at com.vmware.vco.session.impl.VcoSessionFactoryImpl.getVcoServices(VcoSessionFactoryImpl.java:101)

        at com.vmware.vco.adapter.dataservice.RootWorkflowCategoryProcessor.getVcoService(RootWorkflowCategoryProcessor.java:153)

        at com.vmware.vco.adapter.dataservice.RootWorkflowCategoryProcessor.processQuery(RootWorkflowCategoryProcessor.java:136)

        at com.vmware.vco.adapter.dataservice.RootWorkflowCategoryProcessor.getData(RootWorkflowCategoryProcessor.java:63)

        at com.vmware.vise.data.query.impl.DataAdapterUtil.getDataFromAdapter(DataAdapterUtil.java:219)

        at com.vmware.vise.data.query.impl.DataAdapterUtil.getResultFromAdapter(DataAdapterUtil.java:176)

        at com.vmware.vise.data.query.impl.DataAdapterUtil.access$000(DataAdapterUtil.java:43)

        at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:82)

        at com.vmware.vise.data.query.impl.DataAdapterUtil$1.call(DataAdapterUtil.java:79)

        at com.vmware.vise.util.concurrent.ExecutorUtil$2.call(ExecutorUtil.java:769)

        at com.vmware.vise.util.concurrent.ExecutorUtil$ThreadContextPropagatingTask.call(ExecutorUtil.java:1169)

        at com.vmware.vise.data.query.impl.DataServiceThreadPoolDecorator$1.call(DataServiceThreadPoolDecorator.java:173)

        at java.util.concurrent.FutureTask.run(FutureTask.java:266)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

        at java.lang.Thread.run(Thread.java:748)

Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.vco.adapter.http.SamlClientHttpRequestFactory]: Factory method 'newInstance' threw exception; nested exception is java.lang.IllegalArgumentException: Port is invalid

        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189)

        at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588)

        ... 33 common frames omitted

Caused by: java.lang.IllegalArgumentException: Port is invalid

        at org.apache.http.util.Args.check(Args.java:36)

        at org.apache.http.conn.scheme.Scheme.<init>(Scheme.java:93)

        at com.vmware.vco.adapter.http.SamlClientHttpRequestFactory.newInstance(SamlClientHttpRequestFactory.java:196)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:498)

        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:162)

--- @blog https://grzegorzkulikowski.info
Reply
0 Kudos
Grzesiekk
Expert
Expert
Jump to solution

any chance you can tell what is the url for External address to advertise this Orchestrator.

why do we need to put it there, and what does it have to be ? The documentation is really not explaining this, and when i dont type anything in there the plugin in VC side looks like

urlstring"https://10.244.0.123:8281/vco/vsphere-web-client/vco-plugin.zip"

if i put the fqdn is looks like

urlstring"https://vro.infralab.local/vco/vsphere-web-client/vco-plugin.zip"

The fqdn version does not contain any port at all.  not sure if that message about port from webclient has something to do with this port or not.  Thank you for helping me so far.

--- @blog https://grzegorzkulikowski.info
Reply
0 Kudos
iiliev
VMware Employee
VMware Employee
Jump to solution

Ah, yes, I didn't pay attention to the screenshot.

The vRO server port should be 443, not 8281.