VMware {code} Community
vyujs
Enthusiast
Enthusiast

Error downloading plugin package if vCenter and plugin server are installed in a same windows OS with IPv6

Hi,

I setup a vCenter 6.0 on Windows Server 2012 R2. The Internet protocol is set as IPv6 (IPv4 is disabled). This windows joined a domain. And our plugin server is also on this windows OS. After register our plugin to this vCenter, restart vSphere web client service, we cannot see our plugin in Web Client. And got an error in the log:

[2016-12-07T22:00:05.712-08:00] [ERROR] vc-extensionmanager-pool-92  70000068 100004 200001 com.vmware.vise.vim.extension.VcExtensionManager              Package com.ibm.ivp was not installed!

Error downloading https://<FQDN>:<plugin_server_port>/PluginUI.zip. Make sure that the URL is reachable then logout/login to force another download. java.net.ConnectException: Connection refused: connect

    at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)

    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)

    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:344)

    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)

    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)

    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)

    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

    at java.net.Socket.connect(Socket.java:579)

    at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:637)

    at sun.net.NetworkClient.doConnect(NetworkClient.java:175)

    at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)

    at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)

    at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:264)

    at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)

    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)

    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:934)

    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)

    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1302)

    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)

    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)

    at com.vmware.vise.util.http.ConnectionManager.connect(ConnectionManager.java:233)

    at com.vmware.vise.util.http.SimpleHttpClient.connect(SimpleHttpClient.java:218)

    at com.vmware.vise.util.http.SimpleHttpClient.executeMethodResponseAsStream(SimpleHttpClient.java:109)

    at com.vmware.vise.vim.extension.VcExtensionManager.writePackageToFile(VcExtensionManager.java:905)

    at com.vmware.vise.vim.extension.VcExtensionManager.downloadPackage(VcExtensionManager.java:852)

    at com.vmware.vise.vim.extension.VcExtensionManager$1.call(VcExtensionManager.java:671)

    at com.vmware.vise.vim.extension.VcExtensionManager$1.call(VcExtensionManager.java:663)

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

    at com.vmware.vise.util.concurrent.QueuingCachedThreadPool$QueueProcessor.run(QueuingCachedThreadPool.java:866)

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

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

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

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

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

And here are the results I’ve tried:

- Win2k12R2 A

- vCenter 6.0 A installed on Win2k12R2 A

- Plugin A installed on Win2k12R2 A

- Win2k12R2 B

- vCenter 6.0 B installed on Win2k12R2 B

Cases:

(1) Plugin A register to vCenter A

(2) Plugin A register to vCenter B

- [Success] Case #1 and #2 with IPv4

- [Success] Case #2 with IPv6

- [Fail] Case #1 with IPv6, got error log above

Does anybody have idea about this issue?

0 Kudos
7 Replies
laurentsd
VMware Employee
VMware Employee

I'd be interested to hear if other people have run into this IPv6 issue with vSphere 6.0 or 6.5

0 Kudos
vyujs
Enthusiast
Enthusiast

Laurentsd, do you have any ideas about what happened in this case?

0 Kudos
laurentsd
VMware Employee
VMware Employee

No, sorry.  Someone at VMware would have to reproduce it with the right setup,  I filed a bug.

I assume you are not blocked since the work-around is to serve the plugin from a different host, right?

0 Kudos
vyujs
Enthusiast
Enthusiast

0 Kudos
laurentsd
VMware Employee
VMware Employee

No plans yet. This looks like a specific corner case and you have a simple work-around, right?

0 Kudos
vyujs
Enthusiast
Enthusiast

Yes, got it. Thanks a lot.

0 Kudos
tganchev
VMware Employee
VMware Employee

What is the web server you are using to serve the PluginUI.zip to the vSphere Client? I've hit issues where the Tomcat-based containers do not automatically bind to IPv6 loopback address.

What is the output of netstat /anb in this case (for your app server / <port>) on the Windows machine hosting vCenter?

What is the output of nslookup for <FQDN> on the same machine?

Can you do wget / curl for "https://<FQDN>:<plugin_server_port>/PluginUI.zip" successfully?

In the test scenario "Plugin A register to vCenter B" do you log into the client available on vCenter B?

0 Kudos