Fabric operator console cannot start

[thapld]

What happened?

Seems console read wrong config Here DB_CONNECTION_STRING http://couchdb:Ahrl?+6HY,n{fT/8&mzVGOjpQsC9K5PWiX*DL71aB#bR0FxEc^3NMqk4Uduw@2SJ@console-fabric-operations-console--couchdb:5984

What did you expect to happen?

Run successfully

How can we reproduce it (as minimally and precisely as possible)?

openssl genrsa -out ca.key 2048

openssl req -x509 -new -nodes -days 365 -key ca.key -out ca.crt -subj "/CN=console"

kubectl create secret tls console-tls-secret --cert=ca.crt --key=ca.key

kubectl get secrets

export CONSOLE_PASSWORD="admin" export TLS_SECRET_NAME="console-operator-tls" kubectl hlf console create --name=console --namespace=default --version="v1.0.5-30" --image="ghcr.io/hyperledger-labs/fabric-console" \ --admin-user="admin" --admin-pwd="$CONSOLE_PASSWORD" --tls-secret-name="$TLS_SECRET_NAME"

Anything else we need to know?

No response

Kubernetes version

```console # kubectl get nodes -o wide ```

[Linkadi98]

The log from couchdb pod is very clear that it says it has no _userdb then we need to create one in order to start console. But I found a litle bit weird that the couchdb had no admin account so that we cannot access to couchdb api to create new db. I have looked at the source code and find the account of couchdb image is couchdb/couchdb but this account has not worked at all. Have no idea what is going on. The file log.ini inside couchdb pod has a line ;admin=mysecretpassword, this exactly the admin account but it is commented and cannot be use.