Skip to content

OPSC-17911 OpsCenter 6.8.52 release #282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
orion104 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

OPSC-17911 OpsCenter 6.8.52 release #282

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions OpsCenter_6.8_Release_Notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,23 @@ valid updates since 6.8.46 that are not related to the driver upgrade will remai

Significant QA process improvements are in process to avoid similar future issues.

# Release Notes for OpsCenter 6.8.52
30 June 2026

## Backup Service
* Fixed a bug that made OpsCenter unable to work with tables containing vector columns. (OPSC-17965)

## Monitoring
* Reduced the agent logging of the missing metrics from warn to trace. (OPSC-17919)
* Fixed a bug where disk alerts could be triggered when disk usage data was unavailable. (OPSC-17699)

## Provisioning
* Fixed an issue where LCM configuration jobs (install/configure/upgrade) overwrote custom SSL settings in OpsCenter's cluster.conf. The [agents] section's ssl_truststore was incorrectly set to the keystore path. For the [cassandra] section, a new per-cluster setting, "Manage Cassandra SSL" (enabled by default), lets users opt out of LCM managing those SSL settings, preserving any values configured directly in cluster.conf. The setting appears as a checkbox in the Add/Edit Cluster dialog when client encryption is enabled, or can be set via the manage-opsc-cassandra-ssl property in the LCM API. (OPSC-17677)

@annieden annieden Jul 1, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Fixed an issue where LCM configuration jobs (install/configure/upgrade) overwrote custom SSL settings in OpsCenter's cluster.conf. The [agents] section's ssl_truststore was incorrectly set to the keystore path. For the [cassandra] section, a new per-cluster setting, "Manage Cassandra SSL" (enabled by default), lets users opt out of LCM managing those SSL settings, preserving any values configured directly in cluster.conf. The setting appears as a checkbox in the Add/Edit Cluster dialog when client encryption is enabled, or can be set via the manage-opsc-cassandra-ssl property in the LCM API. (OPSC-17677)
* Fixed an issue where LCM install, configure, and upgrade configuration jobs overwrote custom SSL settings in OpsCenter's `cluster.conf`. The `[agents]` section's `ssl_truststore` was incorrectly set to the keystore path. Created a new per-cluster setting, `Manage Cassandra SSL`, enabled by default, in the `[cassandra]` section. This setting allows users to opt out of LCM managing custom SSL settings and preserve any values configured directly in `cluster.conf`. The setting appears as a checkbox in the `Add/Edit Cluster` dialog when client encryption is enabled, or can be set via the `manage-opsc-cassandra-ssl` property in the LCM API. (OPSC-17677)


## Security
* Upgraded dojo, dijit, dojox, and dojo-util to 1.17.3, addressing CVE-2021-23450 (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes Prototype Pollution). (OPSC-17877)

@annieden annieden Jul 1, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Upgraded dojo, dijit, dojox, and dojo-util to 1.17.3, addressing CVE-2021-23450 (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes Prototype Pollution). (OPSC-17877)
* Upgraded `dojo`, `dijit`, `dojox`, and `dojo-util` to version 1.17.3, addressing CVE-2021-23450 (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes Prototype Pollution). (OPSC-17877)

* Updated jackson to version 2.21.4 to address CVE-2026-54512. (OPSC-17976)

@annieden annieden Jul 1, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Updated jackson to version 2.21.4 to address CVE-2026-54512. (OPSC-17976)
* Updated `jackson` to version 2.21.4 to address CVE-2026-54512. (OPSC-17976)


# Release Notes for OpsCenter 6.8.51
28 May 2026

Expand Down