OPSC-17911 OpsCenter 6.8.52 release#282
Open
orion104 wants to merge 1 commit into
Open
Conversation
annieden
reviewed
Jul 1, 2026
| * 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) |
Contributor
There was a problem hiding this comment.
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) |
annieden
reviewed
Jul 1, 2026
| * 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) | ||
|
|
||
| ## 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) |
Contributor
There was a problem hiding this comment.
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) |
annieden
reviewed
Jul 1, 2026
|
|
||
| ## 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) | ||
| * Updated jackson to version 2.21.4 to address CVE-2026-54512. (OPSC-17976) |
Contributor
There was a problem hiding this comment.
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) |
annieden
approved these changes
Jul 1, 2026
annieden
left a comment
annieden
left a comment
Contributor
There was a problem hiding this comment.
Left my suggestions which should be incorporated, but approving for time's sake.
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.