VMware Cloud Foundation

 View Only
  • 1.  VCF Buildout: Preparing Security Requirements for Running Validation Skipped

    Posted Jan 31, 2024 03:34 PM

    VCF version: VMware Cloud Foundation 5.1.0.0-22688368.

    Progress fails at "Preparing Security Requirements for Running Validation" fails with "Skipped" message. Subsequently all other steps failed with "Skipped" message.

    BhojaRavi_0-1706715139745.png

    I have gathered the SSH RSA Key Fingerprints & SSL Thumbprints with the same procedure as in the older versions. Please assist if there is a different way to capture this data.



  • 2.  RE: VCF Buildout: Preparing Security Requirements for Running Validation Skipped

    Posted Feb 01, 2024 09:10 AM

    SSL Thumbprints were gathered using the below command

    openssl x509 -in /etc/vmware/ssl/rui.crt -fingerprint -sha256 -noout

    RSA Key Fingerprints were generated using the below command.

    /usr/lib/vmware/openssh/bin/ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub



  • 3.  RE: VCF Buildout: Preparing Security Requirements for Running Validation Skipped
    Best Answer

    Posted Feb 01, 2024 01:29 PM

     

    Referred - https://kb.vmware.com/s/article/83524. That helped to get past the error.



  • 4.  RE: VCF Buildout: Preparing Security Requirements for Running Validation Skipped

    Posted Apr 18, 2025 04:01 AM

    Hi All, 

    I am facing the seame error message when I trying to deploy VCF 5.2 using suggested file config (Work book). 

    Unfortunately the posted how seems was a good answer for that, was removed. 

    Thank you for your help. 




  • 5.  RE: VCF Buildout: Preparing Security Requirements for Running Validation Skipped

    Posted 29 days ago

    I faced the same error. Upon checking the vcf-bringup-debug.log I could see errors "Certificate doesn't match any of the subject alternative names"
    Followed this KB to fix the issue https://knowledge.broadcom.com/external/article/386968 
    My problem was the Domain Name wasn't configured on the host properly causing the Alternate name to be different than the FQDN. They both have to match to ensure the Validation passes.