[Bug] the chain NNN is stored in shard XXX but is configured for shard YYY

[madumas]

Bug report

After the graphman command change-shard is used to move a chain NNN to a different shard, graph-node complains on start with the error the chain NNN is stored in shard XXX but is configured for shard YYY.

Other than the error message at startup, graph-node runs as expected, using the chain stored on the new shard.

graph-node 0.40.0

Relevant log output

graphman -c /etc/graph-node/config.toml chain change-shard avalanche shard18
Changing block cache shard for avalanche to shard18
Current shard: primary
Changed block cache shard for avalanche from primary to shard18
Segmentation fault (core dumped)



graphman -c /etc/graph-node/config.toml chain list
        name         |   shard    | namespace  | version | head block
---------------------+------------+------------+---------+-----------
avalanche            | shard18    | chain35    |   43114 |   69541463
avalanche-old        | primary    | chain3     |   43114 |   69541151



graph-node output:

Sep 30 12:55:53.868 DEBG Database setup finished, component: ConnectionPool > Coordinator
Sep 30 12:55:53.868 INFO Setup finished, shards: 21
Sep 30 12:55:53.868 DEBG Cleaning up large notifications after about 300s, channel: chain_head_updates, component: ChainHeadUpdateListener > NotificationListener
Sep 30 12:55:53.983 ERRO the chain avalanche is stored in shard shard18 but is configured for shard primary, component: BlockStore

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• [ ] Tick this box if this bug is caused by a regression found in the latest release.
• [ ] Tick this box if this bug is specific to the hosted service.
• [x] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None