Release 3.2.6 #3724
Closed
Release 3.2.6 #3724
Conversation
This file contains 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
|
@karol-kokoszka can we also include #3697 in this release? |
|
Ofc. Will add it |
karol-kokoszka
force-pushed
the
release_3.2.6
branch
from
0c16331 to
6b4c33c
Compare
Newer Scylla versions (e.g. 2024) docker images don't run ssh server on them own, but we require it for some of SM tests.
Because of problems with restoring backups into Scylla 5.4 with raft schema enabled (#3662), we want to test the following workaround: - use fresh cluster without raft schema - restore as usual - enable raft schema in the cluster In order to do that, we leave raft schema on src cluster and test how it works with raft schema enabled/disabled on dst cluster.
Removing filtering was done so that our tests can pass with Scylla 5.4 and raft enabled, but it didn't improve the real life situations where agents don't have cross region remote location access.
…ing CQL SSL Previously, SSL was preferred when client_encryption_options.enabled coming from ScyllaDB configuration was true and SSL port is open, even when Scylla Manager did not have any client certificate registered for particular cluster. This caused issues when ScyllaDB cluster was exposing both CQL and CQL SSL with mTLS, because even when Manager was not registered with certificates, it still insisted to establish sessions using SSL port. CQL healthchecks was also affected. Fixes #3698
"/storage_service/describe_ring/" returns the token range of a
random keyspace. this API is never used in production. what is used
is is cousin which accepts a mandatory keyspace path parameter, like
"/storage_service/describe_ring/{keyspace}", so let's drop it in
scylla-manager, we will drop this API in scylla as well.
Signed-off-by: Kefu Chai <[email protected]>
…use non SSL port on cluster Manager 3.2.6 gives a possibility of explicitly disabling TLS on session even though the certificate and key are available `force_tls_disabled`. Besides that, there is an option to force session to always use non-tls port from scylla config `force_non_ssl_session_port`.
…bled and --force-non-ssl-session-port flags
…on from DB This addresses #3679 .
It adds information about `force-tls-disabled` and `force-non-ssl-session-port` flags.
…-port cluster properties
The fix for #3707 includes extending the cluster kept in the DB with the 'host' property, which represents the initial host used when adding a cluster to Scylla Manager. Scylla-operator passes the DNS name here, making it immune to the ephemeral IPs in the Kubernetes environment. This commit adds the initial host as the first host to query in order to discover node IPs.
…ndpoint This endpoint returns 'consistent_cluster_management' option from scylla.yaml.
karol-kokoszka
force-pushed
the
release_3.2.6
branch
from
f34082f to
2825354
Compare
Also, add timeout on first node setup, as misconfiguration could lead to hanging at this step.
karol-kokoszka
force-pushed
the
release_3.2.6
branch
from
25fbe8f to
70cab79
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 3.2.6
Please make sure that: