-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Jenkins 2.111
Java 8.x
vSphere plugin 2.17
Upgraded from vSphere plugin 2.16 > 2.17 and we can no longer connect to vSphere. Among other things, certificate errors and illegal characters warnings. We have several systems worldwide that have been running for a very many years, and this could end up being problematic.
I suspect it has to do with our naming of jenkins_us1 (the underscore) but that is not clear. To change the name of all of our jenkins, vSphere,and VM instances starts a domino effect that will not be pretty.