shard0 upgrade fail for upgrading 2023.4.2 -> 2024.1.0 but shard1 ok (could not bootstrap consensus)

[jun0tpyrc]

Describe the bug A clear and concise description of what the bug is.

To Reproduce

could not bootstrap consensuscontext deadline exceeded

shard1 is fine , shard0 seems problematic

both run with

--network=mainnet --config=/opt/conf/harmony.conf --run=explorer --run.shard=0 --datadir=/opt/data/ --rpc.ratelimiter=false --http.ip=0.0.0.0 --ws.ip=0.0.0.0

(diff in shard=0 or 1 param only)

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS: [Linux, MacOS]
  • Go environment [ go env ]

Additional context Add any other context about the problem here.

[jun0tpyrc]

custom config:

traceenable=true nostaking=true nodetype=explorer

empty localaccountsfile

1)falling back image to 2023.4.2 and 2)config version 2.6.1->2.5.7, then it's working again but not coming-hardfork-safe i suppose

[sophoah]

hey it's a known issue and is actually random because of an instability of the mainnet bootnode.

please upgrade to v2024.1.0 and restart your node every 3-5 min if you keep having peer issue. User have been reported it should work in a time frame between 2 and 30 min after the first restart

Let me know if you have further issue

[jun0tpyrc]

verified working as said