What's new
- Supports managing ACOS 6.2 U1 clusters.
- Supports modifying the virtual machine network of observability service VMs via API.
Improvement
Optimized the port configuration for AOC to access clusters, changing the default port from 80 to 443.
Resolved issues
- For a cluster with Boost mode enabled, if a virtual machine had a CD-ROM on an IDE bus, hot migration across clusters was incorrectly rejected. The issue has been resolved in this release.
- When the number of available load balancer licenses was 0, editing the gateway of an LB instance (an operation that does not consume additional licenses) incorrectly prompted "The license quota for load balancers is insufficient." The issue has been resolved in this release.
- When expanding a node whose operating system was deployed on a dedicated disk, the expansion failed because the write cache policy of the hardware RAID was empty. The issue has been resolved in this release.
- After a file controller was taken offline, it automatically came back online when the physical node it resided on restarted. The issue has been resolved in this release.
- After a backup task failed to stop, it could not be stopped again. The issue has been resolved in this release.
- When there was an incomplete edit task for an asynchronous replication plan, initiating another edit task might have caused data exceptions. The issue has been resolved in this release.
- When an asynchronous replication plan contained a large number of replication objects, creating a replication task might have failed due to request processing timeout. The issue has been resolved in this release.
- In bulk failover scenarios, the volume replication license usage might have been calculated incorrectly. The issue has been resolved in this release.
- When abnormal backup or replication services existed, upgrading AOC might have caused backup or replication functionality to become abnormal. The issue has been resolved in this release.
- When editing the backup schedule of a backup plan, removing a time point might have displayed an incorrect error message. The issue has been resolved in this release.
- When editing an outgoing replication plan, switching the IP mapping rules from VLAN network to VPC network type might have incorrectly displayed names. The issue has been resolved in this release.
- Backup or replication tasks might have failed to terminate normally due to exceptions. The issue has been resolved in this release.
