Release Notes

Fixed in release 1.1

The following are known issues that have been fixed in EVO:RAIL release 1.1:

• When a second appliance is added to an EVO:RAIL cluster, the ESXi host does not get updated license

information through the EVO:RAIL engine (1404510). See the VMware Knowledge Base article

2101839.

• You must turn on each node separately in an EVO:RAIL appliance with a 10-second delay between

each turn-on. If the nodes are turned on at the same time or too close together, certain race

conditions can occur. For resolution, see the VMware Knowledge Base article 2108864.

• Clicking the logout button displays an error message in Internet Explorer (1382393). For resolution,

see the VMware Knowledge Base article 2106732.

• Under certain conditions EVO:RAIL Configuration can take 45 minutes or longer (1389974). For

resolution, see the VMware Knowledge Base article 2107249.

• EVO:RAIL Configuration might fails with an error message Could not register: License not

available.

• The vCenter Server evaluation period starts when the EVO:RAIL appliance is initially turned on. If the

appliance is not configured in this 60 day period, the error message occurs. For resolution, see the

VMware Knowledge Base article 2108768.

• EVO:RAIL Configuration allows user to upload out of date configuration file. For resolution, see the

VMware Knowledge Base article 2108787.

• Network Time Protocol (NTP) service does not restart automatically on ESXi hosts that are running on

an EVO:RAIL appliance. For resolution, see the VMware Knowledge Base article 2107258.

• Configuring EVO:RAIL might fail with the error message Error creating storage policy under

certain race conditions. This error message can still occur if there is a VSAN configuration issue.

(1425937, 1413059)