Hello,
I am having trouble when attempting to deploy VIO with AD integration. I am able to successfully deploy VIO without AD as an authentication source. However, when I attempt to deploy VIO with AD as an authentication source right at about 85% I get an error in the /var/log/jarvis/ansible.log:
>> 2016-04-14 17:29:11,597 p=354 u=jarvis | TASK: [config-controller | create keystone endpoint] **************************
>> 2016-04-14 17:29:12,737 p=354 u=jarvis | changed: [172.22.33.31]
>> 2016-04-14 17:29:12,738 p=354 u=jarvis | TASK: [config-controller | create services tenant] ****************************
>> 2016-04-14 17:29:13,714 p=354 u=jarvis | changed: [172.22.33.31]
>> 2016-04-14 17:29:13,715 p=354 u=jarvis | TASK: [config-controller | grant service role to service user on service tenant] ***
>> 2016-04-14 17:29:15,152 p=354 u=jarvis | failed: [172.22.33.31] => {"failed": true}
>> 2016-04-14 17:29:15,153 p=354 u=jarvis | msg: exception: name
>> 2016-04-14 17:29:15,154 p=354 u=jarvis | FATAL: all hosts have already failed -- aborting
I've tried googling this error and was brought to this thread: VIO Installation issue - Status: Bootstrap Failed at Controller Node but he's actually getting an LDAP error that I am not.
That thread suggests checking the keystone log, but there is not keystone directory on my VIO Appliance:
>> root@localhost:~# ls /var/log/keystone
>> ls: cannot access /var/log/keystone: No such file or directory
So I'm stumped.
This ended up being a misconfiguration of AD options.
keystone logs would be in the controller VMs. you can ssh into the controller from oms and check the keystone logs there
This ended up being a misconfiguration of AD options.