Westend Coretime state_traceBlock RPC throws Cannot resolve a block range for certain blocks

[kukabi]

Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Description of bug

JSON-RPC request sent over wss to a Westend Coretime archive node version polkadot-parachain 1.17.0-967989c5d94 for block 4150505:

{
    "id": 1,
    "jsonrpc": "2.0",
    "method": "state_traceBlock",
    "params": [
        "0xab6bf79291ff772c3bec130d821f790b292232cfe0d0a759a053c53616fe59bb",
        "state",
        "",
        "Put,ChildPut,ChildKill,ClearPrefix,ChildClearPrefix,Append"
    ]
}

Response:

{
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
        "code": 4001,
        "message": "Cannot resolve a block range ['\"0xab6bf79291ff772c3bec130d821f790b292232cfe0d0a759a053c53616fe59bb\"' ... '\"None\"]. Dispatch error: Failed to collect traces and execute block: Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed\nWASM backtrace:\nerror while executing at wasm backtrace:\n    0: 0x6c49 - coretime_westend_runtime.wasm!rust_begin_unwind\n    1: 0x25dc - coretime_westend_runtime.wasm!core::panicking::panic_fmt::hde8b7aa66e2831e1\n    2: 0x21b6b7 - coretime_westend_runtime.wasm!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::execute_block::h78a33f93d6ba1713\n    3: 0x27d59d - coretime_westend_runtime.wasm!Core_execute_block"
    }
}

Node parameters (public-addr is arbitrary):

./polkadot-parachain \
  --sync=full \
  --state-pruning=archive \
  --blocks-pruning=archive \
  --relay-chain-rpc-urls=wss://rpc.ibp.network/westend \
  --name="coretime-westend-archive-01" \
  --chain=coretime-westend \
  --base-path=/n01/data \
  --public-addr=/ip4/100.100.100.100/tcp/9000 \
  --listen-addr=/ip4/0.0.0.0/tcp/9000 \
  --rpc-port=9001 \
  --rpc-external \
  --rpc-cors=all \
  --rpc-methods=unsafe \
  --unsafe-rpc-external \
  --in-peers=20 \
  --out-peers=20 \
  --prometheus-port=9002 \
  --prometheus-external \
  --telemetry-url="wss://telemetry-backend.w3f.community/submit 1" \
  --db-cache=1024 \
  --rpc-max-request-size=5 \
  --rpc-max-response-size=32 \
  --rpc-max-subscriptions-per-connection=512 \
  --rpc-max-connections=10000 \
  --no-mdns \
  --max-blocks-per-request=32 \
  --no-hardware-benchmarks

It seems that the issue is happening with the blocks that contain the Broker.Interlace extrinsic.

Steps to reproduce

1. Sync a Westend Coretime archive node using the parameters in the issue.
2. Make the RPC call as described in the issue.