Skip to content

Fix CHASM completion fallback after failover reset - #12182

Draft
tekkaya wants to merge 1 commit into
mainfrom
gokhan/nexus-chasm-token-hsm-nonzero-failover
Draft

tekkaya wants to merge 1 commit into
mainfrom
gokhan/nexus-chasm-token-hsm-nonzero-failover

Conversation

@tekkaya

@tekkaya tekkaya commented Sep 19, 2026

Copy link
Copy Markdown
Contributor

What changed?

Describe what has changed in this PR.

Why?

Tell your future self why have you made these changes.

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

Potential risks

Any change is risky. Identify all risks you are aware of. If none, remove this section.

@tekkaya
tekkaya force-pushed the gokhan/nexus-chasm-token-hsm-nonzero-failover branch from 0a2e874 to 73741f8 Compare September 19, 2026 03:45

// TestHSMTokenCompletesHSMOperationAfterResetWithNonzeroFailoverVersion verifies that the native
// HSM reset fallback remains valid when failover changes the namespace version before reset.
func (s *NexusStateReplicationSuite) TestHSMTokenCompletesHSMOperationAfterResetWithNonzeroFailoverVersion() {

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

this passes without the code, added here to show the existing behaviour of hsm to hsm failover and reset scenario.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant