Zesty Disk for standalone instances v24.21
- 1 Minute to read
- Print
- PDF
Zesty Disk for standalone instances v24.21
- 1 Minute to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Release notes v24.21
Release v24.21 includes Zesty Disk Agent v6.8.0 and additional improvements.
Agent v6.8.0
The Agent release includes the following new features, enhancements, and fixes:
New features
Zesty Disk on Windows now supports expanding and shrinking of existing filesystems.
For more information, see How Zesty Disk works.For easier removal of the Zesty Disk Agent, an uninstall command was added to the zestyctl CLI.
Enhancements
Support was added for Ubuntu v24.04.
For faster troubleshooting of installation issues, additional log files were added.
To enable restoring default Agent configurations (such as base URL and API key) during installation, the “reset” flag was added to the installation script.
When you run EZswitch from the CLI, it now automatically creates a new EBS, makes an AWS snapshot before migrating, and deletes the old EBS at the end of the process.
Fixes
Automatic Agent upgrade doesn’t always succeed. (If the current Agent is not automatically upgraded to v6.8.0, install v6.8.0, as described in Install the Zesty Disk Agent on standalone instances.)
The presentation of EZswitch statuses is sometimes delayed in the Zesty platform.
EZswitch starts for some instances even though they are not supported (partitions and LVM).
Reinstalling the Agent on Ubuntu instances sometimes fails.
When the name of a Zesty Disk mount point (for example /data) is part of the name of another mount point (for example /metadata), the Zesty Disk mount point was not remounted after rebooting the instance.
When an instance has a high CPU load, the Zesty Disk sometimes expands, even when there is no need.
The Zesty Disk Agent logs are duplicated to the root logger.
Additional improvements
This release includes the following enhancement:
Enhancement
When defining a “Minimum buffer size” policy in the Zesty Disk > Policies tab, you can now define that as a percentage of provisioned size (in addition to the current GB definition).
Was this article helpful?