Failed to find installed chaincode
@dnakashima is already working on this.
Since Mar 25, 2024.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the deployment using the listed ff deploy fabric dev command and compare its installed-chaincode lookup with the preceding peer lifecycle chaincode queryinstalled --output json output. Trace the CLI entry point handling installation and querying, then determine why the reported package is not found; done means the reproduced deployment recognizes the newly installed chaincode or reports a clear actionable error.
Written by the indexing model from the issue text.
Description
Hi, i can't deploy chaincode,
here my environment version:
- peer:
Version: 2.2.9
Commit SHA: 5305a89
Go version: go1.18.7
OS/Arch: linux/amd64
Chaincode:
Base Docker Label: org.hyperledger.fabric
Docker Namespace: hyperledger - using fabric samples 2.2.9
- go version go1.14 linux/amd64
Step to reproduced:
prifalab@H-LAPTOP-122:~cd fabric-samples2.2.9/asset-transfer-basic/chaincode-go
prifalab@H-LAPTOP-122:~/fabric-samples-2.2.9/asset-transfer-basic/chaincode-go$ touch core.yaml
prifalab@H-LAPTOP-122:~/fabric-samples-2.2.9/asset-transfer-basic/chaincode-go$ peer lifecycle chaincode package -p . --label asset_transfer ./asset_transfer.zip
prifalab@H-LAPTOP-122:~/fabric-samples-2.2.9/asset-transfer-basic/chaincode-go$ ff deploy fabric dev asset_transfer.zip firefly asset_transfer 1.0 -v
installing chaincode
/usr/bin/docker run --platform linux/amd64 --rm --network=dev_default -e CORE_PEER_ADDRESS=fabric_peer:7051 -e CORE_PEER_TLS_ENABLED=true -e CORE_PEER_TLS_ROOTCERT_FILE=/etc/firefly/organizations/peerOrganizations/org1.example.com/peers/fabric_peer.org1.example.com/tls/ca.crt -e CORE_PEER_LOCALMSPID=Org1MSP -e CORE_PEER_MSPCONFIGPATH=/etc/firefly/organizations/peerOrganizations/org1.example.com/users/[email protected]/msp -v /home/prifalab/fabric-samples-2.2.9/asset-transfer-basic/chaincode-go/asset_transfer.zip:/package.tar.gz -v dev_firefly_fabric:/etc/firefly hyperledger/fabric-tools:2.3 peer lifecycle chaincode install /package.tar.gz
2024-01-11 11:31:36.271 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 001 Installed remotely: response:<status:200 payload:"\nOasset_transfer:792716372afe1321577882e8698479732192208d526c8f54321063edd82ab4ae\022\016asset_transfer" >
2024-01-11 11:31:36.271 UTC [cli.lifecycle.chaincode] submitInstallProposal -> INFO 002 Chaincode code package identifier: asset_transfer:792716372afe1321577882e8698479732192208d526c8f54321063edd82ab4ae
querying installed chaincode
/usr/bin/docker run --platform linux/amd64 --rm --network=dev_default -e CORE_PEER_ADDRESS=fabric_peer:7051 -e CORE_PEER_TLS_ENABLED=true -e CORE_PEER_TLS_ROOTCERT_FILE=/etc/firefly/organizations/peerOrganizations/org1.example.com/peers/fabric_peer.org1.example.com/tls/ca.crt -e CORE_PEER_LOCALMSPID=Org1MSP -e CORE_PEER_MSPCONFIGPATH=/etc/firefly/organizations/peerOrganizations/org1.example.com/users/[email protected]/msp -v dev_firefly_fabric:/etc/firefly hyperledger/fabric-tools:2.3 peer lifecycle chaincode queryinstalled --output json
{
"installed_chaincodes": [
{
"package_id": "firefly_1.0:b8e754685421dd03e40251b9ef2dd811e49659453cd489ca7bd27585d9be06b4",
"label": "firefly_1.0",
"references": {
"firefly": {
"chaincodes": [
{
"name": "firefly",
"version": "1.0"
}
]
}
}
},
{
"package_id": "asset_transfer:792716372afe1321577882e8698479732192208d526c8f54321063edd82ab4ae",
"label": "asset_transfer"
}
]
}
Error: failed to find installed chaincode```
- Dominant language
- Go
- Stars
- 66
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hyperledger-firefly/cli
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
hyperledger-firefly/cli#357 ·
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hyperledger-firefly/cli#343 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
hyperledger-firefly/cli#339 · 7 comments ·
-
bug Windows WSL
Difficulty 3/5 1-2 days Newbie friendliness 25/100
hyperledger-firefly/cli#335 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
hyperledger-firefly/cli#334 · 2 comments ·
All issues in hyperledger-firefly/cli
Similar issues
-
feature suggestion
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openvibely/openvibely#1526 ·
Maintainers usually reply within 1 day
-
docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Usenova-Labs/usenova-backend#36 ·
Maintainers usually reply within 1 day
-
bug raised-by:verifier
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
medici-finance/assay#4177 ·
Maintainers usually reply within 1 day
-
bug: admin user creation silently ignores rolePossibly taken @bfs2021 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
eugenioenko/autentico#553 ·
Maintainers usually reply within 1 day
-
sidecar: --moriio-parallel-dispatch omits remote_request_id, so a vLLM NixlPushConnector decode dies with KeyErrorPossibly taken @xintin claimed this today. Openkind/bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
llm-d/llm-d-router#3607 ·
Maintainers usually reply within 1 day