I found these errors in the vm-support.tgz the deployment wizard spits out. Any ideas?
File name is: eam_firstboot.py_4782_stderr.log
2019-02-06T19:30:17.034Z Error during EAM extension registration in VC.
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:726)
2019-02-06T19:30:17.041Z Traceback (most recent call last):
File "/usr/lib/vmware-eam/firstboot/eam_firstboot.py", line 355, in main
fb.registerExtension()
File "/usr/lib/vmware-eam/firstboot/eaminstall/utils.py", line 36, in wrapped_f
raiseNested(_e, exc_info())
File "/usr/lib/vmware-eam/firstboot/eaminstall/utils.py", line 26, in wrapped_f
return f(*args, **kwargs)
File "/usr/lib/vmware-eam/firstboot/eam_firstboot.py", line 173, in registerExtension
self._rhttp_port)
File "/usr/lib/vmware-eam/firstboot/eaminstall/ext_registration.py", line 82, in registerExtension
vpxdKeyFilePath)
File "/usr/lib/vmware-eam/firstboot/eaminstall/extension/extensionRegistrator.py", line 95, in registerExtensionVpxdCertAndKey
self._vc.loginAsInternalExtension(vpxdCertificateFilePath, vpxdPrivateKeyFilePath)
File "/usr/lib/vmware-eam/firstboot/eaminstall/extension/vCenter.py", line 128, in loginAsInternalExtension
self._retrieveServiceContent(stub)
File "/usr/lib/vmware-eam/firstboot/eaminstall/extension/vCenter.py", line 223, in _retrieveServiceContent
), exc_info())
File "/usr/lib/vmware-eam/firstboot/eaminstall/extension/vCenter.py", line 217, in _retrieveServiceContent
self.siC = si.RetrieveContent()
File "/usr/lib/vmware-eam/firstboot/eaminstall/extension/pyVmomi/VmomiSupport.py", line 557, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/usr/lib/vmware-eam/firstboot/eaminstall/extension/pyVmomi/VmomiSupport.py", line 363, in _InvokeMethod
return self._stub.InvokeMethod(self, info, args)
File "/usr/lib/vmware-eam/firstboot/eaminstall/extension/pyVmomi/SoapAdapter.py", line 1407, in InvokeMethod
conn = self.GetConnection()
File "/usr/lib/vmware-eam/firstboot/eaminstall/extension/pyVmomi/SoapAdapter.py", line 1473, in GetConnection
result = self.scheme(self.host, **self.schemeArgs)
File "/usr/lib/vmware-eam/firstboot/eaminstall/extension/pyVmomi/SoapAdapter.py", line 1143, in __call__
server_hostname=host)
File "/usr/lib/python2.7/ssl.py", line 393, in wrap_socket
_context=self)
File "/usr/lib/python2.7/ssl.py", line 641, in __init__
self.do_handshake()
File "/usr/lib/python2.7/ssl.py", line 870, in do_handshake
self._sslobj.do_handshake()
BaseInstallException: {
"resolution": {
"id": "install.eam.fileSR.resolution",
"localized": "Search for these symptoms in the VMware knowledge base for any known issues and possible workarounds. If none can be found, collect a support bundle and open a support request.",
"translatable": "Search for these symptoms in the VMware knowledge base for any known issues and possible workarounds. If none can be found, collect a support bundle and open a support request."
},
"detail": [
{
"args": [
"localhost",
80
],
"id": "install.eam.error.extension.service_content",
"localized": "Cannot retrieve service content from vCenter Server localhost:80.",
"translatable": "Cannot retrieve service content from vCenter Server %(0)s:%(1)s."
},
{
"args": [],
"id": "install.eam.error.extension",
"localized": "Unable to register ESX Agent Manager as an extension in vCenter Server.",
"translatable": "Unable to register ESX Agent Manager as an extension in vCenter Server."
}
],
"componentKey": "eam",
"problemId": null
}
2019-02-06T19:30:17.041Z VMware ESX Agent Manager firstboot failed.
Any ideas?
I'm having the same problem when attempting to upgrade from 6.0 to vCSA 6.7.0 U1b.
wreedMH if you're getting this failure on a new install of vCSA 6.5, we need to examine your setup method and the values you're providing. Something is likely going wrong there. Alternatively, you're welcome to open a SR with GSS to determine root cause.
GSS is currently at a loss. These are new vcenters but joined to an existing PSC domain with 6 others.
I need to deploy two new ones, the first vcenter which would have been the 7th, installed with no issue. The 8th is throwing this error. Only difference is the 7th was registered to the PSCs on site B, while the 8th goes to our A location PSCs.
I tired to deploy 5 times. All pre-school things like time sync, forward and reverse dns have all been tripled checked.
Ok, if you already have something going with GSS then stay the course. They're a much better option than here when it comes to support.
Yeah I hear you but not really.
20,000+ VM view deployment stumps most of them unless we talk to developers...
but this is a vcenter error hoping someone came across before
I fixed it on my own. The PSCs cert had been reset some time ago by another engineer and did not have the FQDN of it in the SAN section. I ran "/usr/lib/vmware-vmca/bin/certificate-manager" on the PSC, Option 4. My other PSCs looked OK, so I left them alone.
After that my install Succeeded.
So I ran into this error below again last night trying to upgrade a External PSC vCenter from VCSA 6.5 to 6.7.
I ended up fixing it by resetting the Machine and Solution user certs on the source vCenter server. I am just posting this in case anyone comes across this. Vmware support was stumped for 5 hours. I ended up fixing myself again.