minifabric icon indicating copy to clipboard operation
minifabric copied to clipboard

Error when provisioning Fabric 2.5.0

Open maciejjedrzejczyk opened this issue 1 year ago • 1 comments

** Brief Description of the issue **

When running Hyperledger Fabric 2.5.0 with a -i switch command, I am encountering the following error:

# Use fabric tools container to create channel artifacts ******
  non-zero return code
  2023-04-18 22:37:32.645 UTC 0001 INFO [common.tools.configtxgen] main -> Loading configuration
  2023-04-18 22:37:32.700 UTC 0002 PANI [common.tools.configtxgen.localconfig] Load -> Could not find profile: OrdererGenesis
  2023-04-18 22:37:32.700 UTC 0003 ERRO [common.tools.configtxgen] func1 -> Could not find profile: OrdererGenesis. Please make sure that FABRIC_CFG_PATH or -configPath is set to a path which contains configtx.yaml with the specified profile
  2023-04-18 22:37:32.759 UTC 0001 INFO [common.tools.configtxgen] main -> Loading configuration
  2023-04-18 22:37:32.801 UTC 0002 INFO [common.tools.configtxgen.localconfig] completeInitialization -> orderer type: solo
  2023-04-18 22:37:32.802 UTC 0003 INFO [common.tools.configtxgen.localconfig] LoadTopLevel -> Loaded configuration: /var/hyperledger/fabric/config/configtx.yaml
  2023-04-18 22:37:32.802 UTC 0004 FATA [common.tools.configtxgen] main -> Error on printOrg: organization org0-example-com not found
  2023-04-18 22:37:32.860 UTC 0001 INFO [common.tools.configtxgen] main -> Loading configuration
  2023-04-18 22:37:32.902 UTC 0002 INFO [common.tools.configtxgen.localconfig] completeInitialization -> orderer type: solo
  2023-04-18 22:37:32.902 UTC 0003 INFO [common.tools.configtxgen.localconfig] LoadTopLevel -> Loaded configuration: /var/hyperledger/fabric/config/configtx.yaml
  2023-04-18 22:37:32.902 UTC 0004 FATA [common.tools.configtxgen] main -> Error on printOrg: organization org1-example-com not found

However, when I inspect configtx.yaml generated by minifabric and placed in vars folder, I clearly see OrdererGenesis section.

I am using a default spec.

** How to reproduce an issue **

Launch a new network with minifab up -i 2.5 command.

maciejjedrzejczyk avatar Apr 18 '23 22:04 maciejjedrzejczyk