Fix console CouchDB connection error (Issue #1179)#1403
Conversation
Addresses issue hyperledger#1233. Adds a new README.md for the sample and updates the root README.md to include asset history and TypeScript support. Signed-off-by: SurbhiAgarwal1 <agarwalsurbhi1807@gmail.com>
…to console Signed-off-by: SurbhiAgarwal1 <agarwalsurbhi1807@gmail.com>
26cbc1f to
dfbcff3
Compare
bestbeforetoday
left a comment
bestbeforetoday
left a comment
There was a problem hiding this comment.
Thank you for the contribution. It seems that most of the automated build workflows did not trigger for this pull request. Perhaps you could amend the last commit — no changes necessary — and force-push to your PR branch to re-trigger the build pipeline.
There are some suggestions for small changes in comment that you might want to make but I am OK to merge this PR as-is once we have a passing build.
| ./network.sh deployCC -ccn ledger -ccp ../asset-transfer-ledger-queries/chaincode-typescript/ -ccl typescript | ||
| ``` | ||
|
|
||
| 3. Run the application (from the `asset-transfer-ledger-queries/application-javascript` folder). |
There was a problem hiding this comment.
It would be great to also include the steps to run the Java version of the client application here. The command (from the application-java directory would be:
./gradlew run| ```shell | ||
| cd application-javascript | ||
| npm install | ||
| node app.js |
There was a problem hiding this comment.
You might consider renaming the run script with the Node applications package.json file to start, which would be consistent with most of the other samples. The command to launch the application would then be:
npm start
|
@SurbhiAgarwal1 In addition to the console CouchDB change, this PR looks to include the commit from PR #1402. The comments I made above actually apply to that commit. You might consider including only the PR for the CouchDB change in this PR rather than both commits. You could achieve that by resetting your local PR branch to the state of the main branch in this repository, then cherry-pick only your commit dfbcff3 to that branch. |
2 participants
Description
This PR resolves Issue #1179 where the Fabric Operations Console fails to start due to a CouchDB connection error (
ECONNREFUSED).Changes
connectionStringto theIBPConsoleresource. This ensures the console uses pre-defined credentials (admin:password) immediately upon startup, eliminating the race condition with the operator's automatic credential generation.storage.couchdbconfiguration to the manifest to ensure stable persistent storage for the database sidecar across all Kubernetes distributions.Benefit
These changes ensure that
just consolereliably reaches theReadystate without getting stuck or failing to connect to its internal database.Fixes: #1179