Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jq error (redis.port) #987

Closed
jc-lab opened this issue Mar 8, 2020 · 2 comments
Closed

jq error (redis.port) #987

jc-lab opened this issue Mar 8, 2020 · 2 comments
Labels

Comments

@jc-lab
Copy link

jc-lab commented Mar 8, 2020

Hello,
I installed zenko with helm (The symptoms are the same for both 1.1.6 and 1.2.0.)

$ helm install https://github.com/scality/Zenko/releases/download/1.2.0-rc.3/zenko-helm-chart-1.2.0-rc.3.tgz

But in some pods I get the following error:

jq: error: syntax error, unexpected ':', expecting $end (Unix shell quoting issues?) at <top-level>, line 1:
. | .kafka.hosts="...-zenko-zenko-queue:9092" | .redis.port=tcp://10.244.153.77:6379 | .queuePopulator.logSource="mongo" | .queuePopulator.mongo.replicaSetHosts="...-zenko-mongodb-replicaset-0....-zenko-mongodb-replicaset:27017,zeronsoftn-local-zenko-mongodb-replicaset-1....-zenko-mongodb-replicaset:27017" | .s3.host="..." | .s3.port="80"                                                                            
jq: 1 compile error

Error in applying redis port in docker-entrypoint.sh.

Problem deployments are listed below:

  • backbeat-gc-consumer
  • backbeat-lifecycle-object-processor
  • backbeat-lifecycle-conductor
  • s3-data

I seem the below issue.
scality/cloudserver#1723

cloudstorage(s3-data) doesn't seem to have a problem with one replica, but backbeat has multiple replicas.
Is it ok to have redis on every pod, as in the above solution?

@rahulreddy
Copy link
Collaborator

@jc-lab Sorry this is coming a bit late, were you able to resolve this issue? I am curious which K8s and helm chart versions you are using.

@rahulreddy
Copy link
Collaborator

rahulreddy commented Feb 3, 2021

Sorry @jc-lab I am closing this issue as there is no response. Please reopen if you are facing the issue again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant