Repository navigation
test(smoke): Apply Secret before HiveCluster to prevent a second ControllerRevision - #793
Merged
Merged
Conversation
sbernauer
reviewed
Nov 10, 2026
…ond ControllerRevision" This reverts commit de1b772.
sbernauer
approved these changes
Nov 10, 2026
sbernauer
left a comment
Member
There was a problem hiding this comment.
Thanks for fixing this! Funny this does not happen locally
Member
Author
Yeah, my guess is that locally, the initial reconcile of both the HiveCluster (creating an STS) and commons operator (adding the restarter label) happen before a ControllerRevision is created. I would have expected the reverse, where the local API server isn't very busy and should reconcile STSs quickly. |
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
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.
This was failing on AKS clusters due to a change in metadata.labels leading to a second ControllerRevision (when we assert
metadata.generation == 1).I have tested this again for one version to ensure it helped: