Skip to content

[BUG] - can't get to Babbage PV8 on node with preliminary Conway support #4978

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

Closed
mkoura opened this issue Mar 13, 2023 · 3 comments
Closed
Labels
cardano-node era: babbage Stale type: bug Something is not working type: regression A feature that worked before stoped working user type: internal Created by an IOG employee

Comments

@mkoura
Copy link
Contributor

mkoura commented Mar 13, 2023

Internal

Area
Other Any other topic (Delegation, Ranking, ...).

Summary
On a node with preliminary Conway support, I can't get to era with Babbage protocol version 8.
The issue happens only on local cluster that updates to PV8 using update proposal. Local cluster that uses TestBabbageHardForkAtEpoch works ok.

It doesn't make any difference if I set TestEnableDevelopmentHardForkEras to true or not. There is a difference in behavior depending on TestEnableDevelopmentNetworkProtocols settings.

With TestEnableDevelopmentNetworkProtocols: true, I can reach epoch where protocol version is supposed to be set to 8, but have following issue:

cardano-cli query protocol-parameters --testnet-magic 42
Command failed: query protocol-parameters   Error: Consensus mode and era mismatch. Consensus mode: CardanoMode Era: ConwayEra

Without TestEnableDevelopmentNetworkProtocols: true, after reaching the epoch where protocol version is supposed to be set to 8, no more blocks are produced and the chain is not progressing. I have following errors in log files:

[bender-3:cardano.node.ErrorPolicy:Error:59] [2023-03-13 11:18:42.70 UTC] IP 127.0.0.1:41449 ErrorPolicyUnhandledApplicationException (HardForkEncoderDisabledEra (SingleEraInfo {singleEraName = "Conway"}))

System info:

@mkoura mkoura added type: bug Something is not working cardano-node era: babbage user type: internal Created by an IOG employee type: regression A feature that worked before stoped working labels Mar 13, 2023
mkoura added a commit to IntersectMBO/cardano-node-tests that referenced this issue Mar 15, 2023
@keyflux
Copy link

keyflux commented Apr 13, 2023

https://rhizome.cloud may help you. There's a ADA public node.

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label May 14, 2023
@mkoura
Copy link
Contributor Author

mkoura commented May 15, 2023

It is already fixed in 8.0.0 and master.

@mkoura mkoura closed this as completed May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cardano-node era: babbage Stale type: bug Something is not working type: regression A feature that worked before stoped working user type: internal Created by an IOG employee
Projects
None yet
Development

No branches or pull requests

2 participants