Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When rebuilding a node, if the password is not _already_ the password of the anvil-join-anvil call fails #843

Open
digimer opened this issue Feb 20, 2025 · 1 comment
Assignees
Labels
pending test automation the issue requires a test written in CI to avoid regressions priority high To be resolved once all urgent issues are clear ready for testing set by dev when issue is ready to be tested by qe

Comments

@digimer
Copy link
Member

digimer commented Feb 20, 2025

The surviving node can't log into the rebuilt node because it doesn't know the peer's password.

The best fix is to have the rebuilt node update it's password to the anvil_password value at the start of the anvil-join-anvil run.

@digimer digimer added bug priority high To be resolved once all urgent issues are clear labels Feb 20, 2025
@digimer digimer added this to the 3.2 Beta - blockers milestone Feb 20, 2025
@digimer digimer self-assigned this Feb 20, 2025
digimer pushed a commit that referenced this issue Feb 21, 2025
address issue #843

Signed-off-by: Madison Kelly <mkelly@alteeve.com>
@digimer digimer removed the bug label Feb 25, 2025
@digimer
Copy link
Member Author

digimer commented Feb 25, 2025

Confirmed fixed.

@digimer digimer added ready for testing set by dev when issue is ready to be tested by qe pending test automation the issue requires a test written in CI to avoid regressions and removed priority high To be resolved once all urgent issues are clear labels Feb 25, 2025
@digimer digimer modified the milestones: Parking lot, 3.2 Beta Feb 25, 2025
@fabbione fabbione modified the milestones: 3.2 Beta, 3.2 Feature Freeze Feb 26, 2025
@fabbione fabbione added the priority high To be resolved once all urgent issues are clear label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending test automation the issue requires a test written in CI to avoid regressions priority high To be resolved once all urgent issues are clear ready for testing set by dev when issue is ready to be tested by qe
Projects
None yet
Development

No branches or pull requests

2 participants