3 Replies Latest reply on Jul 10, 2018 5:45 PM by neyla12

    [vCF 2.3.1] vRA Deployment error

    YC_Hyun Lurker

      Hi all.

      I would like to ask those who have similar experience.

      What should I check to resolve the errors in this step?

       

      1. vRA deployment failed through SDDC Manager.

      vRA Error.PNG

       

      2. evosddc-debug.log :

       

      2018-05-31 23:54:35.579 [https-jsse-nio-8443-exec-16] ERROR [com.vmware.vrack.vrm.security.websso.util.RequestAuthorizationUtility] Not all pre-authorization conditions met for URL /vrm-ui/api/1.0/lcm/bundles called from 172.16.16.200

      2018-05-31 23:54:35.579 [https-jsse-nio-8443-exec-24] ERROR [com.vmware.vrack.vrm.security.websso.util.RequestAuthorizationUtility] Not all pre-authorization conditions met for URL /vrm-ui/api/1.0/lcm/inventory/upgrades called from 172.16.16.200

      2018-05-31 23:54:35.590 [https-jsse-nio-8443-exec-20] ERROR [com.vmware.vrack.vrm.security.websso.util.RequestAuthorizationUtility] Not all pre-authorization conditions met for URL /vrm-ui/api/1.0/lcm/inventory/upgrades called from 172.16.16.200

      2018-05-31 23:54:35.591 [https-jsse-nio-8443-exec-23] ERROR [com.vmware.vrack.vrm.security.websso.util.RequestAuthorizationUtility] Not all pre-authorization conditions met for URL /vrm-ui/api/1.0/lcm/bundles called from 172.16.16.200

      2018-05-31 23:55:18.956 [https-jsse-nio-8443-exec-15] ERROR [com.vmware.vrack.vrm.security.websso.util.RequestAuthorizationUtility] Not all pre-authorization conditions met for URL /vrm-ui/api/1.0/core/activity/vrack/workflows called from 172.16.16.200

       

      3. Environment

      vCF version : 2.3.1

      Work-VM : 172.16.16.200

      I checked Deploy vRealize Automation in Cloud Foundation 

       

      Prerequisites

       

      • Verify that you have created an Active Directory account.You must create an Active Directory (AD) user account with permission to join Windows VMs to the domain.
      • Verify that you have a valid license key for vRealize Automation, which is purchased separately from Cloud Foundation.
      • Verify certificate and private key.You must have a multi-SAN certificate and private key generated by a trusted certificate authority. During generation, you must specify the short and full names of all vRealize Automation VMs and load balancer servers.  >> Used vRealize Certificate Generation Tool VMware Knowledge Base
      • Verify that you have created a subzone in the Active Directory DNS.
      • Verify that Microsoft SQL Server is configured properly.You must join the Microsoft SQL Server VM to the Active AD, create a new login for the AD administrative user in SQL Server, modify the firewall and port configuration, and create the SQL database.
      • Verify that you have an OVA template for the vRealize Automation Windows VM, using Windows 2012 R2.
      • Verify that your Windows server image meet the following requirement for IaaS.

       

      Thank you

      - Hyun