Orchestrator 7.01 Not Registering With vCenter 6 u2 appliance

[VballGuy001]

Hi All,

I'm trying to get Orchestrator 7.01 working with our vCenter 6 u2 appliance. The workflows to "Add a vCenter Server instance" and to "Register vCenter Orchestrator as a vCenter Server extension" say they complete successfully. The vCenter instance shows up in Orchestrator after the Add workflow. In the vCenter web client, I go to Home/vRealize Orchestrator and all I see is the Getting Started page. For some reason I don't know, Orchestrator is not getting registered as an extension in vCenter. I've verified this from http://vcenter/mob. Has anyone seen this/know what the issue is?

I've enabled TLS 1 on the Orchestrator appliance to try to eliminate this as an issue.

Any help would be greatly appreciated.

thanks,

Brian

[iiliev]

Hi,

Check that the user/service account used to communicate with vCenter has enough access permissions there; creating/modifying extension requires certain lever of privileges.

Also, check vRO logs (eg. /var/log/vco/app-server/server.log) for errors/exceptions around the time the workflow to register the extension has been run/completed.

[VballGuy001]

Sorry for the slow response, it's been crazy here the last week. The account that I was using is a member of the administrators group in vCenter. I have excerpted the logs that you mentioned and pasted below for further review, it shows that it failed early on but I don't see a clear reason why:

2016-06-28 22:20:47.547+0000 [http-nio-0.0.0.0-8281-exec-3] INFO  {} [Execution] Executing workflow 'Register vCenter Orchestrator as a vCenter Server extension'

2016-06-28 22:20:47.562+0000 [org.springframework.jms.listener.DefaultMessageListenerContainer#0-1] INFO  {} [Execution] Invoking workflow handler.8ab2c14b559908d901559919b83d001c

2016-06-28 22:20:48.587+0000 [WorkflowExecutorPool-Thread-3] INFO {MYUSERID@COMPANY.COM:Register vCenter Orchestrator as a vCenter Server extension:b9c6000b-3c54-4734-a739-84e6b9c2b425:token=8ab2c14b559908d901559919b83d001c} [WorkflowHandler] Starting workflow 'Register vCenter Orchestrator as a vCenter Server extension' (8ab2c14b559908d901559919b83d001c)...

2016-06-28 22:20:48.595+0000 [WorkflowExecutorPool-Thread-3] INFO {MYUSERID@COMPANY.COM:Register vCenter Orchestrator as a vCenter Server extension:b9c6000b-3c54-4734-a739-84e6b9c2b425:token=8ab2c14b559908d901559919b83d001c} [VimPluginFactory] VimPluginFactory() finished in 2 ms; tokenPrincipal: MYUSERID@COMPANY.COM; sessionId: cf3864e3-fc59-411e-8215-03923cb6e8ae

2016-06-28 22:20:48.665+0000 [WorkflowExecutorPool-Thread-3] INFO {MYUSERID@COMPANY.COM:Register vCenter Orchestrator as a vCenter Server extension:b9c6000b-3c54-4734-a739-84e6b9c2b425:token=8ab2c14b559908d901559919b83d001c} [VlsiHelper] Logging into 'VMware vCenter Server 6.0.0 build-3634794' at https://vCenterserver.company.local:443/sdk with username administrator@company.local

2016-06-28 22:20:48.786+0000 [WorkflowExecutorPool-Thread-3] ERROR {MYUSERID@COMPANY.COM:Register vCenter Orchestrator as a vCenter Server extension:b9c6000b-3c54-4734-a739-84e6b9c2b425:token=8ab2c14b559908d901559919b83d001c} [HostConfigurationUtil] Register as vCenter extension failed

(vmodl.fault.InvalidArgument) {

faultCause = null,

faultMessage = null,

invalidProperty = extension.server.url

}

     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

     at java.lang.reflect.Constructor.newInstance(Constructor.java:423)

     at java.lang.Class.newInstance(Class.java:442)

     at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:173)

     at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:26)

     at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:31)

     at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:141)

     at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:102)

     at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:89)

     at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:84)

     at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:41)

     at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:112)

     at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:273)

     at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:230)

     at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:144)

     at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:51)

     at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:186)

     at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:77)

     at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:581)

     at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:562)

     at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:348)

     at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:308)

     at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:182)

     at com.sun.proxy.$Proxy342.registerExtension(Unknown Source)

     at com.vmware.o11n.cis.VcoinExtensionHelper.registerVcoServer(VcoinExtensionHelper.java:141)

     at com.vmware.vmo.plugin.vi4.config.HostConfigurationUtil.registerVcenterExtension(HostConfigurationUtil.java:265)

     at com.vmware.vmo.plugin.vi4.VMwareInfrastructure.registerExtension(VMwareInfrastructure.java:582)

     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 ch.dunes.vso.sdk.WrappedJavaMethod.invoke(WrappedJavaMethod.java:217)

     at ch.dunes.vso.sdk.WrappedJavaMethod.call(WrappedJavaMethod.java:165)

     at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1473)

     at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:815)

     at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:109)

     at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)

     at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)

     at org.mozilla.javascript.InterpretedFunction.exec(InterpretedFunction.java:120)

     at ch.dunes.scripting.server.script.MainScriptingObject.executeScript(MainScriptingObject.java:255)

     at ch.dunes.scripting.server.script.MainScriptingObject.executeScript(MainScriptingObject.java:241)

     at ch.dunes.workflow.engine.mbean.WorkflowScriptRunner.execute(WorkflowScriptRunner.java:188)

     at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(WorkflowItemTaskRunner.java:44)

     at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(WorkflowItemTaskRunner.java:25)

     at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.executeItem(WorkflowHandler.java:1108)

     at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.requestElementExecution(WorkflowHandler.java:1071)

     at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleWorkflowTokenNextStep(WorkflowHandler.java:779)

     at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.executeToken(WorkflowHandler.java:666)

     at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleTokenExecution(WorkflowHandler.java:601)

     at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.access$100(WorkflowHandler.java:114)

     at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler$1.execute(WorkflowHandler.java:397)

     at ch.dunes.model.ar.AccessRightsTemplate.executeWithAccessRights(AccessRightsTemplate.java:16)

     at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.doExecute(WorkflowHandler.java:393)

     at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.run(WorkflowHandler.java:264)

     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

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

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

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

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

2016-06-28 22:20:48.808+0000 [WorkflowExecutorPool-Thread-3] WARN  {MYUSERID@COMPANY.COM:Register vCenter Orchestrator as a vCenter Server extension:b9c6000b-3c54-4734-a739-84e6b9c2b425:token=8ab2c14b559908d901559919b83d001c} [HttpConfigurationCompilerBase$ConnectionMonitorThreadBase] Shutting down the connection monitor.

2016-06-28 22:20:48.827+0000 [WorkflowExecutorPool-Thread-3] INFO {MYUSERID@COMPANY.COM:Register vCenter Orchestrator as a vCenter Server extension:b9c6000b-3c54-4734-a739-84e6b9c2b425:token=8ab2c14b559908d901559919b83d001c} [SCRIPTING_LOG] [Register vCenter Orchestrator as a vCenter Server extension (6/28/16 22:20:47)] Registered this extension with host myvcenter@company.com

2016-06-28 22:20:48.942+0000 [WorkflowExecutorPool-Thread-3] INFO {MYUSERID@COMPANY.COM:Register vCenter Orchestrator as a vCenter Server extension:b9c6000b-3c54-4734-a739-84e6b9c2b425:token=8ab2c14b559908d901559919b83d001c} [WorkflowHandler] End of workflow 'Register vCenter Orchestrator as a vCenter Server extension' (8ab2c14b559908d901559919b83d001c), state: completed

2016-06-28 22:20:49.340+0000 [PolicyLogCenter-JMS-Sender] INFO 

[iiliev]

Hmm, I'm not sure what exactly this error 'invalidProperty = extension.server.url' means. Two possibilities come in mind:

1) Something got wrong with your vCenter setup. Are you able to browse other registered extensions? Open https://vCenterserver.company.local/mob then click 'content' -> 'ExtensionManager', and you should see a list with other registered extensions. Click on them, and find if some have a clickable property 'server' which in turn has property 'url'.

2) Another possibility is that we pass an invalid value for this extension.server.url property. Registration logic enumerates all IP addresses available on the machine and uses these IP addresses as an input when registering extension, so it is possible, although highly unlikely, that some IP is treated as invalid by vCenter.

[VballGuy001]

I am able to browse the vCenter extensions:

I'm not sure where I would see the invalid IP that might get passed.

[iiliev · Accepted solution]

OK, it seems this error happens when you provide a non well-formed value for the second input parameter of the workflow 'Register Orchestrator as vCenter Server extension' (the parameter labelled 'External address to advertise this Orchestrator').

If you provide the address in a format like sample.domain.com or 10.20.22.23, the workflow will complete successfully but extension will not be registered, and the error will appear in the logs.

The correct format would be something like https://sample.domain.com:8281 or https://10.20.22.23:8281 (that is, a full URL specifying scheme, address/ip, and port).

Another option would be to try to left the second input parameter blank, in which case the workflow will try to register multiple URLs for each network interface on your machine, but this could be problematic in some cases, especially with IPv6 interfaces.

[VballGuy001]

That was it Illian. You beat VMware tech support by 19 minutes to the answer. The document I was using to do the install had just shown it as the sample.domain.com format.

Thanks again,

Brian