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.

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

Post a Comment

Popular posts from this blog

HPE Nimble Storage AF60 on Speed!

-
Image
 I am just finishing the upgrade of a pair of Nimble AF60 All Flash arrays to now run with an SCM Module for even better performance and I wanted to share the installation steps and some first impressions. Adding SCM is as of now only possible to AF60 and AF80 Systems and requires a minimum software version of 5.2. There is a good post from Stephen that is detailed what´s all about: https://community.hpe.com/t5/around-the-storage-block/accelerate-transactional-workloads-with-storage-class-memory/ba-p/7090551 The SCM modules are 1,5 TB Intel Optane Cards in a PCIe x4 formfactor so you need at least one free slot in your AF to get things going. Recommendation is also to use Slot 2 for the SCM Module. Installation process in a rough overview is as following: Update to 5.2 if you haven´t done yet halt standby controller unplug cables from the halted controller and remove it from the chassis insert SCM card to the controller plug controller and cables back in and wait for it to be booted an
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!
Read more