TOOL-558: fix paasta status during migrations#4249
Open
gmdfalk wants to merge 1 commit into
Open
Conversation
Signed-off-by: Max Falk <gfalk@yelp.com>
nemacysts
reviewed
Feb 20, 2026
nemacysts
left a comment
nemacysts
left a comment
Member
There was a problem hiding this comment.
i would personally prefer that we have duplicate instances for as short a period as possible - but if this (where "this" is having duplicates for an extended period of time) is necessary for y'all's migration process, i think i'd be fine with merging if we all pinky-promise that we'll revert this PR once we're done :)
Contributor
Author
I think we can live with paasta status temporarily not working |
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.
Problem
During the migration of Cassandra to EKS, we have duplicate CassandraCluster configurations, one on legacy clusters, one on new clusters.
But currently
paasta statuswill only return the status of a single instance in the dict which is the EKS one, if it exists.Ideally, we can see the status of both.
Solution
Make a backwards-compatible change that just creates a list with two entries and returns the status for both if more than one instance with the same name exist.
Signed-off-by: Max Falk gfalk@yelp.com