VMware Aria Automation Tools

 View Only
Expand all | Collapse all

vCAC 6.0 Appliance - Registered Service "iaas-service" shows as FAILED following installation of VCAC 6.0 (Complete Install)?

  • 1.  vCAC 6.0 Appliance - Registered Service "iaas-service" shows as FAILED following installation of VCAC 6.0 (Complete Install)?

    Posted Jan 09, 2014 09:12 AM

    I'm new to vCAC 6.0 however I just want to make sure the service below is not going to cause me issues going forward.

    REGISTERED SERVICES on the vCAC 6.0 Appliance shows the "IAAS-Service" as FAILED. Can't really find any info on VMWARE site on what this does. The install looks good so far - ie all the web pages are working as designed. I've followed the docs and also this doc http://vpirate.in/category/vcac-6-0/

    Anyone who has done a vCAC 6.0 install have any feedback on what their system says?

    Thank you.



  • 2.  RE: vCAC 6.0 Appliance - Registered Service "iaas-service" shows as FAILED following installation of VCAC 6.0 (Complete Install)?

    Posted Jan 09, 2014 09:45 AM

    This may not be an issue since it may be working. The status of the service changes depending on how I access the web page.

    When I access my vCAC web console using SHORTNAME it says it is REGISTERED. When I access using the FQDN is says FAILED.

    Example below:

    1)      Access using SHORTNAME,     https://vcac:5480

             Results in:    

        

    1)      Access using FQDN,     https://vcac.mydomain.com:5480

             Results in:    

        

    Interesting, but strange. Don't understand what the service does yet but maybe will become apparent later as I start to configure the product. 



  • 3.  RE: vCAC 6.0 Appliance - Registered Service "iaas-service" shows as FAILED following installation of VCAC 6.0 (Complete Install)?

    Broadcom Employee
    Posted Jan 09, 2014 10:07 PM

    The IaaS Service is needed for your out-of-box Infrastructure provisioning (ie the vCAC 5.x functionality).  So pretty important :-)  The FQDN should always be used when ever the server name needs to be entered during the installation. And this is also important when you access the application, especially the first time!  I would be concerned that DNS isn't working completely properly here as the windows IaaS server may not be able to access the vCAC VA properly once you log in and start using the tool. You should know fairly quickly - once you have a tenant set up and log in as Fabric / Tenant admin and try accessing the Infrastructure tab.