Symptoms
In Horizon DaaS 8.0, appliances such as Secondary Service Provider, Resource Manager and Tenant deployment fail due to an invalid IPV6 address conversion from the prefix-based MAC addresses.In the desktone.log file, the following entries can be seen.
2019-01-23 04:40:17,359 WARN [com.desktone.vmgr.desktopfactory.vmware.vcenter.DesktopFactoryVCenterImpl]-[pool-127-thread-1] Unable to establish connection with new VM at address 'fe80::168bb:ccff:fedd:ba2d%eth1', could possibly be due to invalid ethernet cards; result: ProcessResult com.desktone.util.ProcessUtil$ProcessResult@607ea7cb
exitValue = 255
stderr = [ssh: Could not resolve hostname fe80::168bb:ccff:fedd:ba2d%eth1: Temporary failure in name resolution]
stdout = []
Under Reservations, you will notice that the task fails at around 45%
Cause
MAC address to IPV6 address conversion logic has an issue.Appliance can't be deployed when it is configured with prefix-based MAC address allocation.It will work for some of the mac addresses for which the hexadecimal and binary value of the first octet will be the same post 6th bit inversion.For example: The following mac addresses will work as the hexadecimal and binary value of first octet will be same post 6th bit inversion. a) 00:05:69 b) 00:0C:29
Resolution
This issue has been fixed in 8.0.1 release. Horizon DaaS 8.0.1 Release Notes
Users were not able to deploy the secondary service provider appliance (SP2) because the IPv6 address was not being generated correctly from the MAC address. This has been fixed so that the IPv6 address now generates correctly and the deployment occurs as expected. [2213658]
