[BUG] - cardano-node 10.1.4 - node log: chunk number repeated in epoch field

[asnakep]

Hello IntersectMBO Team,

we open this issue merely to report the following:

we upgraded our nodes to 10.1.4 and caught a repeated chuck number in epoch field.

Log entries from node start, including a second restart some hours later:

{"app":[],"at":"2025-01-08T11:53:01.639Z","data":{"blockNo":"11322750","chunkNo":"6700","immTip":"674c00b0ff928f9f16b96d18a399f8fcaeaee372ea383950b57244a2b4b44893","kind":"TraceImmutableDBEvent.ValidatedLastLocation"}}
{"app":[],"at":"2025-01-08T11:53:01.640Z","data":{"epoch":"6700","immtip":{"headerHash":"674c00b0ff928f9f16b96d18a399f8fcaeaee372ea383950b57244a2b4b44893","kind":"BlockPoint","slot":144727877},"kind":"TraceOpenEvent.OpenedImmutableDB"}}
{"app":[],"at":"2025-01-08T11:53:01.640Z","data":{"kind":"TraceOpenEvent.StartedOpeningVolatileDB"}}

{"app":[],"at":"2025-01-08T18:50:55.120Z","data":{"blockNo":"11324016","chunkNo":"6701","immTip":"cfd12165fbe705a8ed424dec6e28d7f92ad668c80a9441a2bd1b812afc57c2b4","kind":"TraceImmutableDBEvent.ValidatedLastLocation"}}
{"app":[],"at":"2025-01-08T18:50:55.121Z","data":{"epoch":"6701","immtip":{"headerHash":"cfd12165fbe705a8ed424dec6e28d7f92ad668c80a9441a2bd1b812afc57c2b4","kind":"BlockPoint","slot":144752789},"kind":"TraceOpenEvent.OpenedImmutableDB"}}
{"app":[],"at":"2025-01-08T18:50:55.121Z","data":{"kind":"TraceOpenEvent.StartedOpeningVolatileDB"}}

Kind regards,
Manuel

[karknu]

This is an incorrectly named log field, it was not something introduced in 10.1.4 but an old error that has existed for years.

https://github.com/IntersectMBO/cardano-node/blame/307fdd248603f1af2457e63e443403f072a4a864/cardano-node/src/Cardano/Tracing/OrphanInstances/Consensus.hs#L1140-L1143

[asnakep]

I considered this possibility but I caught that only after last upgrade.