VMware Cloud Community
kalEl00
Contributor
Contributor
‎06-04-2014 11:04 PM

Error adding IaaS host with vCAC 6.0.1 plugin for vCO

I installed the new vCAC 6.0.1 plugin on vCO 5.5 (that comes bundled with vcac). I am able to add the vcac host just fine, but when I try to add the iaas host, I get the attached error -

com.vmware.o11n.plugin.dynamicops.ServiceException: HTTP/1.1 401 Unauthorized : <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="

vcac host = mycompany-vcac-dev01.domain.com

iaas host = mycompany-iaas-dev.domain.com

I know that the account has access to the iaas service and the box, because its a domain administrator. I am able to open up links like https://mycompany-iaas-dev.domain.com/Repository/Data/ManagementModelEntities.svc with that account just fine.

anyone seen this before or know how to move past it?

Thanks in advance.

Preview file
157 KB
4 Replies
sanchezs
VMware Employee
VMware Employee
‎06-04-2014 11:29 PM

That seems an authorization problem accessing the IaaS machine. Verify that the following inputs of the workflow are correct:

  • host
  • authentication user name
  • authentication password
  • domain for NTLM authentication


You can try to run the workflow "Add the IaaS host of a vCAC host" after adding your vCAC host instead of running directly the workflow "Add an IaaS host".

0 Kudos
kalEl00
Contributor
Contributor
‎06-04-2014 11:37 PM

I did try that – here are the results in screenshots (same as before)

Preview file
211 KB
0 Kudos
kalEl00
Contributor
Contributor
‎06-04-2014 11:43 PM

I did try that – here are the results in screenshots (same as before)

Preview file
73 KB
Preview file
67 KB
Preview file
59 KB
Preview file
72 KB
0 Kudos
vSeanClark
Enthusiast
Enthusiast
‎07-07-2014 03:17 PM

This article thread didn't directly help me solve my issue with adding a IaaS host workflow, but it did turn on a lightbulb in my head that I should not fully qualify the username (username@mydomain.com) if I'm asked to specify the NTLM authentication domain later. 

So.. after banging my head against the VMware Authentication Wall of Pain for 2 hours, I just used the simple username in the username field.  And only mydomain.com in the NTLM authentication domain field, and POOF!  Workflow worked just fine and I now have a VCAC IAAS host added was just able to browse the VCAC vm inventory and destroy a VM via vCO workflow. 

VMware authentication consistency has much to be desired.  That is all. 

Sean Clark - http://twitter.com/vseanclark