Downloading the self-signed certificates from your VMware system and configuring your system to consider them trusted should work. The process I use for this is as follows:
$ sudo -i # openssl s_client -connect 10.230.8.210:443 -showcerts < /dev/null # mkdir /usr/share/ca-certificates/custom # nano /usr/share/ca-certificates/custom/vmware.crt <paste certificate> # dpkg-reconfigure ca-certificates Note, however, that this only works if the self-signed SSL certificate for the VMware system has a properly configured common name (or subject alternate name) so that the SSL library can match the IP address or hostname to the connection string. In MAAS 2.x, you can work around this issue by adjusting the power parameters for your VMware servers. In our lab environments, we use the following command line to add a VMware chassis: maas profile machines add-chassis chassis_type=vmware username=vmware- username password=vmware-password protocol='https+unverified' hostname =vmware-api-ip-address prefix_filter=maas (This will add all VMs named "maas*" to MAAS.) See also: https://github.com/vmware/pyvmomi/commit/92c1de5056be7c5390ac2a28eb08ad939a4b7cdd ** Changed in: maas Status: New => Won't Fix ** Changed in: maas (Ubuntu) Status: New => Invalid ** Summary changed: - ssl error vmware vcenter 6 connection + [2.0rc3] SSL verification error when connecting to VMware vCenter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608639 Title: [2.0rc3] SSL verification error when connecting to VMware vCenter To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1608639/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
