Topic not created automatically when using Hedera Local Node

[bpatrzyk]

Problem description

I deployed Guardian and Hedera locally on two separate virtual machines.
I configured Guardian according to the documentation (https://docs.hedera.com/guardian/guardian/readme/getting-started/how-to-configure-hedera-local-node)
I commented the INITIALISATION_TOPIC_ID in the configs/.env.develop.guardian.system file as mentioned in the documentation.

The config looks as follows:

# ------------------------
HEDERA_NET="localnode"

# PRE USED HEDERA_NET
# ---------------------
PREUSED_HEDERA_NET="localnode"

# TESTNET
#OPERATOR_ID="..."
#OPERATOR_KEY="..."

# Create topic using the create-topic script
#INITIALIZATION_TOPIC_ID=""

# # LOCALNODE
LOCALNODE_ADDRESS="192.168.122.102"
LOCALNODE_PROTOCOL="http"
OPERATOR_ID="0.0.2"
OPERATOR_KEY="302e020100300506032b65700422042091132178e72057a1d7528025956fe39b0b847f200ab59b2fdd367017f3087137"

When I was going through the initial configuration wizard in Guardian web app I got the invalid topic id error.
I ended up creating a topic using a nodejs script and provided it in the INITIALISATION_TOPIC_ID variable - this fixed the issue I was able to finish Guardian configuration.

Could you please verify whether there is a problem with automatically creating the topic in such setup?

Step to reproduce

Steps to reproduce the behavior:

1. Deploy Hedera Local Node
2. Deploy Guardian on a different host and point it the Hedera Local Node
3. Go through the initial configuration wizard in the web app
4. The wizard finishes with topic id error.

Expected behavior

Topic is created automatically

[prernaadev01]

@bpatrzyk Thank you raising this ticket.
After discussing it internally, we found out that the issue is with commenting INITIALIZATION_TOPIC_ID. Can you please uncomment it and retry it once as it will be auto generated.