Firefly Core fails to start up - with Error: FF10412: Bad network version

[Timtech4u]

I tried running the Firefly Helm Chart (version 0.6.0) but it failed with the following error:
Error: FF10412: Bad network version: %!!(MISSING)s(<nil>)

I can confirm that Firefly data exchange pods are up and running as seen below:

[onelapahead]

Hey @Timtech4u I'll follow up with you in Hyperledger Discord in the coming days to provide more direct support around this. But a few things to note and ask:

• 0.6.0 is currently not released yet, it's only just been merged into main and we're doing some final testing before releasing it. That being said, really appreciate you testing it in advanced! :)
• If you are able to provide your values.yaml (obfuscate any secret values please) that would be helpful.
• Please provide the image tags that are being used for all the FireFly runtimes you are deploying, even if you aren't overriding image tags. It'll be helpful to know what combination of images you've ended up with.
• The specific error you are encountering Bad network version implies you are running FireFly v1.1.x with an older version of the batch pin contract. As part of 1.1.x it was upgraded, and FireFly supports using multiple versions of the contract across different block numbers. If this is a fresh installation of FireFly, then you'll just need to deploy the new contract and refer to that rather than the old version. If this is a 1.0.x installation from the 0.5.x chart that is being upgraded, see https://github.com/hyperledger/firefly/wiki/Migration-Guide-for-v1.1.0 and the relevant FIR to learn more about the significant changes that came with 1.1.x (which is why we're taking our time w/ 0.6.0, appreciate your patience and help!).

Hope this is helpful, and will try to follow up with you directly soon.

[onelapahead]

Would also appreciate hearing your experience of using the chart in ArgoCD, and if our docs around ArgoCD usage needs any enhancements for the future! 🙇🏻‍♂️

[Timtech4u]

Thank you @hfuss for the reply. I could also request @nguyer adds you to a shared connection on Slack for further chat.
I also got the deployment working by switching to use EVMConnect (shared this with Nicko yesterday).
However, I am currently blocked by self-registration for the default organization & nodes.

With respect to the Batch Pin contract, yes, this was deployed recently using this same smart contract. Can you help confirm if I just need to redeploy the same smart contract or if there is another one? Thank you

[Timtech4u]

Would also appreciate hearing your experience of using the chart in ArgoCD, and if our docs around ArgoCD usage needs any enhancements for the future! 🙇🏻‍♂️

I definitely would be happy to share my experience and contributes to ArgoCD's usage in your documentation here. Hoping to do this soon. cc: @KaamilW