Skip to content

Conversation

@sghosh23
Copy link
Contributor

Change type

  • Fix
  • Feature
  • Documentation
  • Security / Upgrade

Basic information

  • THIS CHANGE REQUIRES A DEPLOYMENT PACKAGE RELEASE
  • THIS CHANGE REQUIRES A WIRE-DOCS RELEASE

Testing

  • I ran/applied the changes myself, in a test environment.
  • The CI job attached to this repo will test it for me.

Tracking

  • I added a new entry in an appropriate subdirectory of changelog.d
  • I mentioned this PR in Jira, OR I mentioned the Jira ticket in this PR.
  • I mentioned this PR in one of the issues attached to one of our repositories.

Knowledge Transfer

  • An Asciinema session is attached to the Jira ticket.

Motivation

Objective

Reason

Use case

@sghosh23 sghosh23 requested review from a team and julialongtin as code owners November 28, 2025 14:32
Updates ansible-cassandra submodule to include:
- Cassandra version 3.11.19
- Updated SHA256 checksum
- HTTPS mirror URL for enhanced security

This resolves the checksum mismatch error during offline deployments.
…checksum format

Updates ansible-cassandra submodule to 6f6e4214 which fixes the cassandra_sha256
checksum format from Nix SRI format (sha256-<base64>) to Ansible format
(sha256:<hex>).

Fixes Ansible error: "The checksum parameter has to be in format <algorithm>:<checksum>"
etcd_download_url: "{{ binaries_url }}/etcd-{{ etcd_version }}-linux-{{ image_arch }}.tar.gz"
nerdctl_download_url: "{{ binaries_url }}/nerdctl-{{ nerdctl_version }}-linux-{{ image_arch }}.tar.gz"
cassandra_url: "{{ binaries_url }}/apache-cassandra-3.11.16-bin.tar.gz"
cassandra_version: "3.11.19"
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we can leave a comment that this version is used by ansible-cassandra submodule can overwrite the value from upstream.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done!

passthru.url = url;
url = "http://archive.apache.org/dist/cassandra/${ cassandra_version }/apache-cassandra-${ cassandra_version }-bin.tar.gz";
sha256 = "sha256-zQHG0SNFMWoflAEzJj7qnShMeiC370XCbxoitbR1/Ag=";
sha256 = "sha256-ZyQJ04BM3enCe0x+na+Q/ccySsbbjyYI4iXysAzUVTQ=";
Copy link
Contributor

Choose a reason for hiding this comment

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

should this sha hash match with upstream hash in ansible-cassandra module?
wireapp/ansible-cassandra@f5c2467...6f6e421#diff-23e21b6c89468f7534697ad091835b3ee5e0213b37ace489488234e5a9548ec4R5

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes

sghosh23 and others added 4 commits January 13, 2026 10:23
…d offline environments

- Fix deprecated 'include:' syntax to 'include_tasks:'
- Fix variable naming: cluster_name -> cassandra_cluster_name
- Fix vars_files path: roles/cassandra -> roles-external/ansible-cassandra
- Add offline mode check for ec2_metadata_facts
- Add dry_run mode for cluster health checks
- Comment out repairs_backups.yml (incompatible with_zip_cycle plugin)
- Fix YAML syntax issues

These changes enable Cassandra upgrade playbooks to work in offline
environments and with Ansible 2.16+.

Tested with rolling restart of 3-node cluster upgrading from 3.11.16
to 3.11.19 with zero data loss.
Add TODO comment explaining that cassandra_restart.yml needs updates
for offline/systemd environments. Document manual restart workaround.
…uide

Add comprehensive upgrade guide for offline environments covering:
- Downloading wire-server-deploy static artifacts from S3
- Copying binaries and ansible files to appropriate hosts
- Running pre-upgrade, installation, restart, and post-upgrade steps
- Verification with nodetool and cqlsh
- Manual rolling restart procedure

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@sonarqubecloud
Copy link

@sghosh23
Copy link
Contributor Author

@mohitrajain thanks for reviewing. Please do a re-check. Added the comment you asked.

@mohitrajain
Copy link
Contributor

Can you please share an asciinema for the migration process on the jira ticket since it can't be verified by our github workflow to understand the new changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants