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.

Sign up for GitHub

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

Jump to bottom

Regression test Crypto-Update-Jar-1.5k-25m failed due to WAIT_FOR_VERSION_AFTER_UPDATE #10255

Closed
JeffreyDallas opened this issue Dec 4, 2023 · 3 comments · Fixed by #10455
Closed

Regression test Crypto-Update-Jar-1.5k-25m failed due to WAIT_FOR_VERSION_AFTER_UPDATE #10255

JeffreyDallas opened this issue Dec 4, 2023 · 3 comments · Fixed by #10455
Assignees
@JeffreyDallas @Neeharika-Sompalli
Labels
Bug An error that causes the feature to behave differently than what was expected based on design.

Comments

@JeffreyDallas
Copy link
Contributor

Description

The test Crypto-Update-Jar-1.5k-25m on all OS variants started failing
due to stuck at the step WAIT_FOR_VERSION_AFTER_UPDATE

https://swirldslabs.slack.com/archives/C03E8SA5UF9/p1701502375257449

---- UpdateReconnectTestStepValidator FAILED validation ----
Error at step: WAIT_FOR_VERSION_AFTER_UPDATE

Steps to reproduce

Nightly test panel GCP-Daily-Update-CentOS7-4N-2C

Additional context

No response

Hedera network

mainnet

Version

latest

Operating system

None
@JeffreyDallas JeffreyDallas self-assigned this Dec 4, 2023
@JeffreyDallas JeffreyDallas added the Bug An error that causes the feature to behave differently than what was expected based on design. label Dec 4, 2023
@JeffreyDallas
Copy link
Contributor Author

JeffreyDallas commented Dec 4, 2023 •
edited
Loading

From initial investigation, it seems after nodes are successfully upgraded,
the client's transaction could not go through, got BUSY response, even when platform status is already ACTIVE

@JeffreyDallas
Copy link
Contributor Author

Further test showed that test failed at PR a7dea9f
(feat: Stop returning token associations and token balances data in queries as per HIP-367 (#10149) )

https://swirldslabs.slack.com/archives/C03G7CBJJ06/p1701726765827489

but was passing at previous PR 282c61e

https://swirldslabs.slack.com/archives/C03G7CBJJ06/p1701725213030659

@Neeharika-Sompalli Neeharika-Sompalli mentioned this issue Dec 12, 2023
Merged
@JeffreyDallas JeffreyDallas reopened this Jan 3, 2024
@JeffreyDallas
Copy link
Contributor Author

Fixed long time ago already

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

@JeffreyDallas JeffreyDallas

@Neeharika-Sompalli Neeharika-Sompalli

Labels
Bug An error that causes the feature to behave differently than what was expected based on design.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Fix regression tests failed due to HapiGetAccountInfo hashgraph/hedera-services
2 participants
@JeffreyDallas @Neeharika-Sompalli