Qumulo Core Feature Log

This section lists the most important features from each release.

Qumulo Core 7.7.4

The majority of functionality and stability improvements in this Qumulo Core release are internal.
Added the /v1/portal/ping REST API endpoint and the qq portal_ping command
Changed how the qq ad_cancel, ad_join, ad_leave, and ad_reconfigure commands return the status of in-progress background operations

Important
This release resolves a kernel incompatibility with hardware platforms that use AMD EPYC 9004 Series (AMD Genoa and later) CPUs.

Significantly improved the performance of the incremental replication process for directories

Important
This release resolves a kernel incompatibility with hardware platforms that use AMD EPYC 9004 Series (AMD Genoa and later) CPUs.

Changed how NFS export host restrictions use KRB* keywords in Qumulo Core by allowing an additional match for hosts that authenticate by using a specific Kerberos flavor
Added REST API endpoints and qq CLI commands to support specifying a registration key that associates your Qumulo cluster with your Qumulo Nexus account
Changed qq CLI error messages to write to stderr instead of stdout
Resolved an S3 API issue with applications placing a trailing whitespace in the signed header field

Important

This release resolves a kernel incompatibility with hardware platforms that use AMD EPYC 9004 Series (AMD Genoa and later) CPUs.
This release resolves an issue where previously it was possible for QFSD to crash when system clock time was moved "backwards" while Cloud Data Fabric (CDF) is enabled for a Qumulo cluster.
To prevent Qumulo Core from consuming a large amount of memory when an Intel NIC is installed in a node, we have blacklisted the irdma kernel module in Qumulo Core 7.7.0 (and higher).

Added Non-VPN Remote Support for self-managed Cloud Native Qumulo (CNQ) and on-premises clusters
Removed and replaced qq CLI commands related to Snapshots functionality
Resolved an issue with case sensitivity in Domain Controller lists

Important

This release resolves an issue with the Qumulo Core upgrade process.
This release resolves unexpected behavior in the latest host operating system which can block the Qumulo Core upgrade process due to temporary storage becoming unavailable.
This release resolves an issue identified in Qumulo Core 7.5.4 where, under certain conditions, a node could become unavailable during an update.

The majority of functionality and stability improvements in this Qumulo Core release are internal.
Resolved an issue with the location of S3 buckets created from the Qumulo Core Web UI

Important

This release resolves an issue with Authoritative DNS (QDNS) by reducing the amount of logging for the feature.
This release resolves a rare issue where previously, under certain conditions, concurrent quorum-related activity could result in file system data being overwritten.
This release resolves an issue that previously occurred after a spoke portal was deleted.
This release resolves the following on-premises cluster issues:
- For clusters with certain erasure coding configurations deployed before July 4, 2020, this release resolves an issue that previously could occur during quorum formation, resulting in internal metadata being in an inconsistent state.
- This release resolves unexpected SAS controller behavior on hardware nodes, where previously hot-plugging drives could cause cluster instability.

Made improvements to Cloud Data Fabric:
- Enabled the creation of up to 32 spoke portals on a single Qumulo cluster
- Improved file creation latency and throughput for spoke portals
- Added the Priority Sync feature for read-write spoke portals
Added the Qumulo Authoritative DNS (QDNS) to Qumulo Core
Added support for latest Western Digital Ultrastar DC SN640 SSD firmware
Resolved an issue with incorrect drive types for nodes in on-premises clusters
Modified the ListBuckets S3 API action to use the BucketPolicy permission together with Role-Based Access Control (RBAC) in Qumulo Core

Important

This release resolves the following on-premises cluster issues:
- This release resolves unexpected SAS controller behavior on hardware nodes, where previously hot-plugging drives could cause cluster instability.
- For clusters with certain erasure coding configurations deployed before July 4, 2020, this release resolves an issue that previously could occur during quorum formation, resulting in internal metadata being in an inconsistent state.
This release resolves a rare issue where previously, under certain conditions, concurrent quorum-related activity could result in file system data being overwritten.
This release resolves an issue that previously occurred after a spoke portal was deleted.

Important
This release resolves the following on-premises cluster issues:

This release resolves unexpected SAS controller behavior on hardware nodes, where previously hot-plugging drives could cause cluster instability.
For clusters with certain erasure coding configurations deployed before July 4, 2020, this release resolves an issue that previously could occur during quorum formation, resulting in internal metadata being in an inconsistent state.

Added the self-service permission model to Qumulo REST API access tokens and made changes to corresponding qq CLI commands
Made it possible for a user to perform operations on their own access keys without having RBAC privileges
Resolved issues concerning cached data on a spoke portal host cluster, directory metadata block updates made by S3 API actions, and the GetObject S3 API action with the Veeam client