hyperledger-labs / minifabric

Do fabric network the right and easy way.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unable to inject new transactions from a secondary node

alphacybercom opened this issue · comments

I managed to connect two nodes A (primary) and B (secondary), with a custom chaincode.

Connection commands (also available in a previous issue) are reported in the following.

# A:
scp ${B_USER}@${B_HOST}:${MINIFAB_FOLDER}/vars/JoinRequest_org2-mydomain-com.json vars/NewOrgJoinRequest.json
sudo ./minifab orgjoin
sudo ./minifab channelquery,configmerge,channelsign,channelupdate
scp vars/profiles/endpoints.yaml ${B_USER}@${B_HOST}:${MINIFAB_FOLDER}/vars/
scp -r vars/chaincode/${CHAINCODENAME}/${CHAINCODENAME}_node_1.0.0.tar.gz ${USER}@${HOST}:${FOLDER}/vars/chaincode/${CHAINCODENAME}

# B:
sudo ./minifab nodeimport,join -c ${CHANNELNAME}
sudo ./minifab discover
sudo ./minifab install,approve -n ${CHAINCODENAME} -p '' -l node -v 1.0.0

# A:
sudo ./minifab approve,discover,commit

# B:
sudo ./minifab anchorupdate
sudo ./minifab profilegen

Under such circumstances, by directly running minifab commands on A, both to retrieve or inject a transaction, everything works as expected.
Instead, on B, I get the following results:

  • transactions retrieval/query is accomplished correctly
  • the injection of new transactions is successful (no errors are returned by minifab), but the transaction is not propagated to A (hence, neither B can't see it): while by injecting a new transaction on A works, the same minifab command, when executed on B, does not change the status of the blockchain

How can I solve this issue?