Bug Fixes

The following bugs have been fixed in the HyWorks v4.1-Hotfix2.1 release:

HyWorks Controller and Server-side Modules

Bug ID	Description
74073	During graceful recompose, HyWorks was cleaning the whole batch even when only one VM in the batch failed to clone. The issue is fixed in this release, where HyWorks will not mark the whole batch as failed on the failure of a single VM.
73850	A scheduled "Move to Version" task could report "Successfully Completed" even though no desktop was actually recomposed to the new version - for example, when the recompose type was set to "only move free VMs" and none were free at the time the schedule ran, the pool was silently left on its old version with no further action taken. Scheduled and manual Move to Version, Recompose, and power operations now complete correctly once a desktop becomes eligible.
73842	HyWorks was not showing any snapshots post upgrade to v4.0/4.1 with Nutanix Prism Element with APIv2 or Nutanix Prism Central with APIv3. The HyWorks Controller now correctly handles any error thrown by Nutanix and shows the relevant error in the logs as per the response received from Nutanix.
72827	The MAC Preserve feature does not work with Clone from Recovery Point when the Nutanix Connector (Prism Central > v7.3) is configured with APIv4 + APIv4.2. APIv4.2 was introduced in HyWorks v4.1-HF2 to mitigate issue #72187 of clone from recovery point. With Hotfix v4.1-HF2.1, clone from recovery point and MAC preserve feature will work together.
-	Multiple bugs are fixed in the following areas: - An administrator cancels pool cloning or recompose operations, and subsequent Move to Version or Recompose operations fail or get stuck with no informative logs. - UI-based restrictions for desktop pools or desktop-based operations for the desktop pools get stuck in some intermediate state, like canceling (HyWorks is attempting to stop the pending cloning jobs).