Conversation
…items there were previously missed.
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
| 5 March 2026 | ||
|
|
||
| ## Backup Service | ||
| * Updated the version of the java aws sdk used by OpsCenter. (OPSC-17745) |
There was a problem hiding this comment.
Suggested change
| * Updated the version of the java aws sdk used by OpsCenter. (OPSC-17745) | |
| * Updated the version of the Java AWS SDK that OpsCenter uses. (OPSC-17745) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
|
|
||
| ## Backup Service | ||
| * Updated the version of the java aws sdk used by OpsCenter. (OPSC-17745) | ||
| * Fixed a bug that could cause the backup status of a node to be switched from “completed” to “running” preventing cleanup from running. (OPSC-17775) |
There was a problem hiding this comment.
Suggested change
| * Fixed a bug that could cause the backup status of a node to be switched from “completed” to “running” preventing cleanup from running. (OPSC-17775) | |
| * Fixed a bug that could cause the backup status of a node to be switched from “completed” to “running” and thus prevent cleanup from running. (OPSC-17775) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
| * Fixed an issue where backup location validation would fail for non-Azure locations. (OPSC-17780) | ||
|
|
||
| ## Best Practice Service | ||
| * The authentication error triggered when a cluster connection attempt is initiated by a Best Practice rule has been downgraded to a non-blocking debug message, preventing false failure notifications. (OPSC-16230) |
There was a problem hiding this comment.
Suggested change
| * The authentication error triggered when a cluster connection attempt is initiated by a Best Practice rule has been downgraded to a non-blocking debug message, preventing false failure notifications. (OPSC-16230) | |
| * The authentication error triggered when a cluster connection attempt is initiated by a Best Practice rule is downgraded to a non-blocking debug message to prevent false failure notifications. (OPSC-16230) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
|
|
||
| ## Best Practice Service | ||
| * The authentication error triggered when a cluster connection attempt is initiated by a Best Practice rule has been downgraded to a non-blocking debug message, preventing false failure notifications. (OPSC-16230) | ||
| * The "Use prepared statements" best practice rule has been updated to correctly handle bind markers, preventing false failures when querying the OpsCenter events table. (OPSC-17777) |
There was a problem hiding this comment.
Suggested change
| * The "Use prepared statements" best practice rule has been updated to correctly handle bind markers, preventing false failures when querying the OpsCenter events table. (OPSC-17777) | |
| * The "Use prepared statements" best practice rule is updated to correctly handle bind markers and prevent false failures when querying the OpsCenter events table. (OPSC-17777) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
| * Removed the deprecated "DataStax public repository" option from LCM as the service is being shut down. (OPSC-17766) | ||
|
|
||
| ## Core | ||
| * Fixed CVE-2023-6378 by upgrading logback library to 1.2.13 (OPSC-17791) |
There was a problem hiding this comment.
Suggested change
| * Fixed CVE-2023-6378 by upgrading logback library to 1.2.13 (OPSC-17791) | |
| * Fixed CVE-2023-6378 by upgrading logback library to v1.2.13. (OPSC-17791) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
|
|
||
| ## Core | ||
| * Fixed CVE-2023-6378 by upgrading logback library to 1.2.13 (OPSC-17791) | ||
| * Fixed CVE-2023-2976 by upgrading Google Guava to 32.0.0-jre (OPSC-17792) |
There was a problem hiding this comment.
Suggested change
| * Fixed CVE-2023-2976 by upgrading Google Guava to 32.0.0-jre (OPSC-17792) | |
| * Fixed CVE-2023-2976 by upgrading Google Guava to version 32.0.0-jre. (OPSC-17792) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
| ## Core | ||
| * Fixed CVE-2023-6378 by upgrading logback library to 1.2.13 (OPSC-17791) | ||
| * Fixed CVE-2023-2976 by upgrading Google Guava to 32.0.0-jre (OPSC-17792) | ||
| * Fixed CVE-2025-48924 by upgrading org.apache.commons:commons-lang to 3:3.20.0 (OPSC-17784) |
There was a problem hiding this comment.
Suggested change
| * Fixed CVE-2025-48924 by upgrading org.apache.commons:commons-lang to 3:3.20.0 (OPSC-17784) | |
| * Fixed CVE-2025-48924 by upgrading org.apache.commons:commons-lang to version 3:3.20.0. (OPSC-17784) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
| * The "Use prepared statements" best practice rule has been updated to correctly handle bind markers, preventing false failures when querying the OpsCenter events table. (OPSC-17777) | ||
|
|
||
| ## Monitoring | ||
| * Fixed an issue where hints-on-disk alerts triggered continuously even with zero hints, disabled alerts, or deleted alerts. (OPSC-17763) |
There was a problem hiding this comment.
Suggested change
| * Fixed an issue where hints-on-disk alerts triggered continuously even with zero hints, disabled alerts, or deleted alerts. (OPSC-17763) | |
| * Fixed an issue where 'hints-on-disk' alerts triggered continuously even with zero hints, disabled alerts, or deleted alerts. (OPSC-17763) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
| * Fixed CVE-2023-6378 by upgrading logback library to 1.2.13 (OPSC-17791) | ||
| * Fixed CVE-2023-2976 by upgrading Google Guava to 32.0.0-jre (OPSC-17792) | ||
| * Fixed CVE-2025-48924 by upgrading org.apache.commons:commons-lang to 3:3.20.0 (OPSC-17784) | ||
| * Upgraded the Cassandra driver used by opscenterd and the agent to 4.x. Local datacenter is now auto-detected. If auto-detection fails, configure `local_dc_pref` in the cluster configuration or via the new "Data Center" field in the UI. (OPSC-17253) |
There was a problem hiding this comment.
Suggested change
| * Upgraded the Cassandra driver used by opscenterd and the agent to 4.x. Local datacenter is now auto-detected. If auto-detection fails, configure `local_dc_pref` in the cluster configuration or via the new "Data Center" field in the UI. (OPSC-17253) | |
| * Upgraded the Cassandra driver used by 'opscenterd' and the agent to v4.x. Local datacenter is now auto-detected. If auto-detection fails, configure `local_dc_pref` in the cluster configuration or through the new "Data Center" field in the User Interface (UI). (OPSC-17253) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
| * Fixed CVE-2025-48924 by upgrading org.apache.commons:commons-lang to 3:3.20.0 (OPSC-17784) | ||
| * Upgraded the Cassandra driver used by opscenterd and the agent to 4.x. Local datacenter is now auto-detected. If auto-detection fails, configure `local_dc_pref` in the cluster configuration or via the new "Data Center" field in the UI. (OPSC-17253) | ||
| * Added SSL truststore and client certificate support to the PostUrl event plugin for secure integration with external HTTPS alerting systems. For full SSL support including SNI, set `enable_curl=True`. (OPSC-17422) | ||
| * Added `azcopy_upload_with_sync` to the agent config with a default of false. When set to true uploads done with azcopy will use a sync command instead of a copy adding another layer of insurance that files will not be uploaded if they are already present on the destination. When using this option it is strongly recommended that the `backup_tmp_dir` be on the cassandra data partition as limitations with azcopy prevent the use of symlinks when staging the files for upload. (OPSC-17716) |
There was a problem hiding this comment.
Suggested change
| * Added `azcopy_upload_with_sync` to the agent config with a default of false. When set to true uploads done with azcopy will use a sync command instead of a copy adding another layer of insurance that files will not be uploaded if they are already present on the destination. When using this option it is strongly recommended that the `backup_tmp_dir` be on the cassandra data partition as limitations with azcopy prevent the use of symlinks when staging the files for upload. (OPSC-17716) | |
| * Added `azcopy_upload_with_sync` to the agent configuration with a default of 'false'. When set to 'true' an 'azcopy' upload uses a 'sync' rather than a 'copy. This adds another layer of insurance that no files are uploaded if they are already present on the destination. When using this option it is strongly recommended that the `backup_tmp_dir` be on the 'cassandra' data partition because limitations with 'azcopy' prevent the use of symlinks when staging the files for upload. (OPSC-17716) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
| * Added SSL truststore and client certificate support to the PostUrl event plugin for secure integration with external HTTPS alerting systems. For full SSL support including SNI, set `enable_curl=True`. (OPSC-17422) | ||
| * Added `azcopy_upload_with_sync` to the agent config with a default of false. When set to true uploads done with azcopy will use a sync command instead of a copy adding another layer of insurance that files will not be uploaded if they are already present on the destination. When using this option it is strongly recommended that the `backup_tmp_dir` be on the cassandra data partition as limitations with azcopy prevent the use of symlinks when staging the files for upload. (OPSC-17716) | ||
| * Fixed an issue where an agent would continuously retry startup if the API port was already in use. (OPSC-17204) | ||
| * Fixed an issue where sessions configured with timeout=0 were unexpectedly garbage-collected under heap pressure. (OPSC-17762) |
There was a problem hiding this comment.
Suggested change
| * Fixed an issue where sessions configured with timeout=0 were unexpectedly garbage-collected under heap pressure. (OPSC-17762) | |
| * Fixed an issue where sessions configured with 'timeout=0' were unexpectedly garbage-collected under heap pressure. (OPSC-17762) |
annieden
reviewed
Mar 4, 2026
OpsCenter_6.8_Release_Notes.md
Outdated
| * Added `azcopy_upload_with_sync` to the agent config with a default of false. When set to true uploads done with azcopy will use a sync command instead of a copy adding another layer of insurance that files will not be uploaded if they are already present on the destination. When using this option it is strongly recommended that the `backup_tmp_dir` be on the cassandra data partition as limitations with azcopy prevent the use of symlinks when staging the files for upload. (OPSC-17716) | ||
| * Fixed an issue where an agent would continuously retry startup if the API port was already in use. (OPSC-17204) | ||
| * Fixed an issue where sessions configured with timeout=0 were unexpectedly garbage-collected under heap pressure. (OPSC-17762) | ||
| * Added a new configuration parameter, `extra_user_search_bases`, in the [ldap] section of the opscenterd.conf file. This parameter allows specifying additional LDAP user search bases for authentication, enabling users from multiple Organizational Units (OUs) to authenticate. The parameter accepts a semicolon-separated list of LDAP search bases. This parameter is optional and backward-compatible with existing configurations. (OPSC-17753) |
There was a problem hiding this comment.
Suggested change
| * Added a new configuration parameter, `extra_user_search_bases`, in the [ldap] section of the opscenterd.conf file. This parameter allows specifying additional LDAP user search bases for authentication, enabling users from multiple Organizational Units (OUs) to authenticate. The parameter accepts a semicolon-separated list of LDAP search bases. This parameter is optional and backward-compatible with existing configurations. (OPSC-17753) | |
| * Added a new configuration parameter, `extra_user_search_bases`, in the [ldap] section of the 'opscenterd.conf' file. Specify additional LDAP user search bases for authentication with this parameter to enable users from multiple Organizational Units (OUs) to authenticate. The parameter accepts a semicolon-separated list of LDAP search bases. This parameter is optional and backward-compatible with existing configurations. (OPSC-17753) |
annieden
requested changes
Mar 4, 2026
annieden
left a comment
annieden
left a comment
There was a problem hiding this comment.
Hi, Orion! I've asked for minor grammatical and tense updates to your RNs. Suggested changes are inline. I can approve once you've reviewed. ~Annette
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release Notes Automation
If you name your pull-request as "Product x.y.z Release ...", after merging the
PR, a GitHub Action will automatically create a product version tag "product-x.y.z".
Supported product names are:
Version supports 3 sets or 4 sets of digits.