[Bug] Moving network subgraph between shards causes empty query / wrong query

[jhjhjh94]

Bug report

Note that this only happens for Graph Network Subgraph. Moving other subgraphs are fine
Currently it's QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv

Steps to reproduce :

1. Sync network subgraph from scratch to any index nodes or shard
2. After synced, try and do a local query using the network subgraph, any types of query that returns some data. Record the data
3. Perform this graphman copy create --replace <sgdXX> <shard_name> <index_node>
4. After copying is done, make sure the original copy is deleted or graphman unused remove. Then repeat Step 2 and compare the data
5. Data returns : {"data":{"subgraphMetadataSearch":[]}}#

My theory : Moving between index nodes is not the issue, but moving between different shards is.
subgraphMetadataSearch returns empty so I think it's IPFS related.

GRAPH_NODE_VERSION="graphprotocol/graph-node:v0.35.1"
INDEXER_SERVICE_VERSION="ghcr.io/graphprotocol/indexer-service-rs:1.3.2"
INDEXER_AGENT_VERSION="ghcr.io/graphprotocol/indexer-agent:v0.21.9"
INDEXER_CLI_VERSION="ghcr.io/graphprotocol/indexer-cli:v0.21.9"
INDEXER_TAP_AGENT_VERSION="ghcr.io/graphprotocol/indexer-tap-agent:v1.7.3"

Relevant log output

No response

IPFS hash

QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv

Subgraph name or link to explorer

https://thegraph.com/explorer/subgraphs/DZz4kDTdmzWLWsV373w2bSmoar3umKKH9y82SUKr5qmp?view=Query&chain=arbitrum-one

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.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

Linux