[BUG] Topology ERROR after a rare transaction

[s8sato]

OS and Environment

Linux, test_env.py

GIT commit hash

76dafdc

Minimum working example / Steps to reproduce

Prepare transaction.json (example) with a few instructions and,

git checkout 76dafdc
cargo build
LOG_LEVEL=ERROR ./scripts/test_env.py --peer-name-as-seed setup
cd test

Repeat the following with a sufficiently long period:

cat transaction.json | ./iroha json transaction

Actual result

Every peer logs a topology ERROR like this:

test/peers/iroha0/log.txt

  2024-08-22T15:26:03.161900Z ERROR iroha_core::sumeragi::main_loop: Topology rotated n times, peer_id: ed012003415E0E516BE83870CE5A2165605E8719216B5ECCCE4AEDFB0B2B77862B3798@@127.0.0.1:1337, prev_role: ProxyTail, next_role: ValidatingPeer, n: 1, view_change_index: 1
    at core/src/sumeragi/main_loop.rs:915

Expected result

There should be no ERROR level logs in normal use

Logs

See Actual result section

Who can help to reproduce?

@s8sato

Notes

No response

[alexstroke1]

No errors on the last main