Vcenter update from VAMI - no updates

[pargit]

hi,

i have vcsa 7u3i in linked mode with another vcsa same version.

when i go to vami update page on the first server i get an empty list, but in the other vc i can see the 7u3j version avaiable.

on the "bad" vcsa when i do check updates i get an error "Check the URL and try again." on the second server it spins and then show the latest avaiable version to update.

the update url on both vc's is the devault:

https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/7.0.3.0110...

the proxy on both vc's is the same without any blocks

it worked before when i upgraded from vcsa 7u2 to 7u3c and then to g, but for the i version i needed to download the patch iso and install that way.

can you point me to whatever might cause this?

"bad" vc:

"good" vc:

thanks

mordechai

[maksym007]

So you are trying to patch vCenter via access to the internet? 

Check first in the environment if you see the pop-up "new vCenter version available."

I would suggest to do this offline with ISO.

[pargit]

in the vcenter ui itself i used to have this message but now i don't see it anymore, instead i get every few minutes this error in the tasks:

Download plug-in

 Cannot complete the operation. See the event log for details. Error downloading plug-in. URL is unreachable. java.net.SocketTimeoutException: connect timed out java.net.PlainSocketImpl.socketConnect(Native Method) java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) java.net.Socket.connect(Socket.java:607) org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:368) org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72) org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:221) org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:165) org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:140) com.vmware.vise.plugin.download.PluginDownloadServiceImpl.downloadPackageInfo(PluginDownloadServiceImpl.java:304) com.vmware.vise.plugin.download.PluginDownloadServiceImpl.download(PluginDownloadServiceImpl.java:170) com.vmware.vise.plugin.async.task.PluginDownloadTask.run(PluginDownloadTask.java:73) java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1640) com.vmware.vise.util.concurrent.QueuingCachedThreadPool$2.call(QueuingCachedThreadPool.java:873) java.util.concurrent.FutureTask.run(FutureTask.java:266) com.vmware.vise.util.concurrent.QueuingCachedThreadPool$QueueProcessor.run(QueuingCachedThreadPool.java:1271) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) com.vmware.vise.util.concurrent.WorkerThreadFactory$1.run(WorkerThreadFactory.java:64) java.lang.Thread.run(Thread.java:750)

VMware Cloud Provider Services Plugin (com.vmware.cloud.provider.services.plugin:1.0.0.0)

i don't know if this is related to the update process.