So this is a fault we've been coming up against over and over, and we don't know the cause.
With have a few vRO setups, but it only happens on one of them (7.4.0)
Problem
Symptoms
Current Workaround
The current workaround is tiresome and not what we want to be doing forever.
Does anyone have any thoughts as to why this happens and how we can stop it from happening?
p.s. the log error that appears is as follows (every 40s or so):
2018-11-01 12:09:29.622+0000 [taskScheduler-6] INFO {} [SessionWrapper] creating server session for Administrator@<DOMAIN>@<VCENTER-SERVER> SDK
2018-11-01 12:09:29.650+0000 [taskScheduler-6] INFO {} [SamlTokenImpl] SAML token for SubjectNameId [value=Administrator@<DOMAIN>, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from XML
2018-11-01 12:09:36.705+0000 [taskScheduler-8] ERROR {} [SessionWrapper] Error occurred when constructing host session for: Administrator@<DOMAIN>@<VCENTER-SERVER>
SDK java.lang.RuntimeException: (vim.fault.InvalidLogin) {
faultCause = null,
faultMessage = null
}
at com.google.common.base.Throwables.propagate(Throwables.java:240)
at com.vmware.o11n.plugin.vsphere.connect.CommonInvocationHandler.invokeTarget(CommonInvocationHandler.java:146)
...
at java.lang.Thread.run(Thread.java:748) Caused by: (vim.fault.InvalidLogin) { faultCause = null, faultMessage = null }
at sun.reflect.GeneratedConstructorAccessor428.newInstance(Unknown Source)
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:174)
...
Just to clarify something about your vRO setup - are all vRO instances of the same version 7.4.0 and only one of them is showing this problem? Or are the other vRO instances of some other versions and only the one with version 7.4.0 is showing the problem?
BTW, if you are willing to test, could you try to update the vCenter plug-in on the problematic vRO instance with the latest tech preview version available at https://communities.vmware.com/docs/DOC-32872 and check if the problem is still there?
We have two 7.4.0 vRO setups (both using VC plugin v6.5.0.7783677)
one is connected to a 6.5 vCenter (The only one with the problem),
while the other is connected to 6.0, 6.5 & 6.7 vCenters - without any problem
we also have a 7.3 vRO setup which also has no such issues
I will download that plugin and let you know if the problem remains.
ok, we've tried that plugin (6.5.0.10376265) and unfortunately we have encountered the issue again