2.3. Resolved Issues

These issues are now resolved in Red Hat Enterprise Virtualization 3.1:
BZ#842344
In previous releases the Manager would attempt to boot virtual machines using an attached disk, in accordance with the user's specified boot order, even when no attached disk was marked as bootable. This behaviour has since changed. Disks for booting virtual machines must be marked as bootable. This includes disks created using the REST API and associated developer tools.
BZ#847733
Previously, adding a host which was already attached to a VLAN tagged network failed. The modifications made to the original configuration script for the ethernet device caused it to lose connectivity. This issue has been resolved, allowing the addition of a host that is already attached to a VLAN tagged network.
BZ#790758
In previous releases the VDSM bootstrap process retrieved utility scripts from the Manager using the HTTP protocol. This exposed virtualization hosts being added to the environment to a potential man in the middle attack. In Red Hat Enterprise Virtualization 3.1 the utility scripts are pushed to hosts using the SSH protocol. This updated bootstrap process prevents man in the middle attacks.