Exception when uploading OVA to vCenter when using Proxy

-
With the recent version vCenter 7.0.0b there seems still being an issue when having HTTP / HTTPS proxy configured and trying to import an OVA / OVF.
This is the error message you will see most likely:

Failed to deploy OVF package. ThrowableProxy.cause A general system error occurred: Transfer failed: Server not trusted: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, note that HTTP/s proxy is configured for the transfer.


A quick workaround is to disable Proxy via VAMI and only enable it when you need id to download updates via Lifecycle Manager or for vCenter updates.

I have a support case open for this, let´s see if there will be a fix soon.

Update, there is a KB out at VMware that you need to specify NO_PROXY according to your environment to get this working again. 

cheers!

Comments

  1. AnonymousSeptember 15, 2020 9:34 PM

    Thank you! My goggling about this eventually led to this post and this is exactly what I am facing too.

    ReplyDelete
  2. AnonymousOctober 27, 2020 12:02 PM

    Thanks a lot.

    ReplyDelete
  3. UnknownDecember 04, 2020 2:38 PM

    Thank you! This resolved my issue too.

    ReplyDelete
  4. UnknownMarch 01, 2021 11:10 PM

    Any update from the VMware case?

    ReplyDelete
    Replies
    1. JohannesMarch 08, 2021 3:46 PM

      Sadly it was closed by: "You are not using a supported proxy setup" as i use a proxy that is not pingable and thus have to configure it via /etc/sysconfig/proxy

      Delete
    2. JohannesMay 27, 2021 10:00 AM

      There is this KB out, and it´s all about setting the NO_PROXY right.
      https://kb.vmware.com/s/article/81565?lang=en_US

      Delete

Post a Comment

Popular posts from this blog

vCenter update stuck "Data conversion/Post install hook failed" and how I fixed it

-
Image
 I was updating a vCenter instance from 7.0 to 7.0.1a but got this error message but everything else seems to work fine.  I just cleared the install state using this procedure  and was able to use VAMI again. Oddly after clearing the update status VAMI was showing the old build number whereas the vSphere Client shows the new one.  After some days there was 7.0.1b released and I tried this again but was stuck again at that point. Just yesterday I tried it again with 7.0.1c but the "Stage" and "Stage and Install" buttons were grayed out. So I digged a little and prepared the VCSA, after that the buttons got clickable again: Backup your appliance first! root@vcsa [ /storage/core/software-update ]# mv install_operation install_operation.bak root@vcsa [ /storage/core/software-update ]# mv stage_install_operation stage_install_operation.bak root@vcsa [ /storage/core/software-update ]# mv stage_operation stage_operation.bak root@vcsa [ /storage/core/software-update/updates
Read more

ESXi Update problem 7.0 to 7.0U1 missing bootbank

-
 After some unsuccesful tries to update 7.0 to U1 i created a case with VMware to show them that i get a totally useless ESXi installation after the update to U1 17119627. The Case took a while but finally there is a workaround out for my specific case, actually i´m not thinking to be that specific as I'm just running ProLiant Gen10 and vSAN in a 10 Node cluster. The problem seems beeing with the software FCoE that i´m not using so it´s easy to just remove it from the configstore prior the update: configstorecli config current delete -c esx -g storage_fcoe -k fcoe_activation_nic_policies --all reboot (important)  update to 7.0U1 as usual There should be a patch out soon that hopefully will address this but meanwhile you can try it this way. cheers! -Update 7.0.1c is fixing this issue so you can easily update now.
Read more