Hi team, I recently updated our acryl-datahub-acti...
# troubleshootl
little-breakfast-38102
08/02/2022, 4:05 AMHi team, I recently updated our acryl-datahub-actions service to use newer version of image and started facing “CrashLoopBackOff” error. Here are the images with versions used in values.yaml
Following is the error message from pod log
2022/08/01 222256 Waiting for: http//health
2032/99022, 32-32 38, 28135 P, dotan'tiP;"éfeal"bet"hittp://eath":nttpinoHost in request UfL. Steeping 15Values.yaml
tag: "V0.8.40"
datahub-gms:
image:
repository: $(cg_image_repo}/linkedin/datahub-gms
datahub-frontend:
image:
repository: ${cg_image_repo}/linkedin/datahub-frontend-react
acryl-datahub-actions:
image:
repository: $(cg_image_repo}/acryldata/datahub-actions
datahub-mae-consumer:
image:
repository: ${cg_image_repo}/linkedin/datahub-mae-consumer
datahub-mce-consumer:
image:
repository: ${cg_image_repo}/Linkedin/datahub-mce-consumer
datahub-ingestion-cron:
image:
repository: $(ecr_image_repo}/acryldata/datahub-ingestion:v0.8.40
#customized by adding additional drivers
elasticsearchSetupJob:
image:
repository: $(cg_image_repo}/Linkedin/datahub-elasticsearch-setup
kafkaSetupJob:
image:
repository: ${cg_image_repo}/Linkedin/datahub-kafka-setup
mysqlSetupJob:
image:
repository: $(cg_image_repo}/acryldata/datahub-mysql-setup
postgresqlSetupJob:
image:
repository: $(cg_image_repo}/acryldata/datahub-postgres-setup
datahubUpgrade:
image:
repository: ${cg_image_repo}/acryldata/datahub-upgradeAppreciate any help.
little-breakfast-38102
08/02/2022, 7:05 PMI see following env variables passed on in the pod
GMS_HOST: catalog-datahub-gms
GMS_PORT: 8080
Here is how my deployment.yaml looks like
env:
• name: DATAHUB_GMS_HOST
value: (( printf "SS-ss" •Release.Name "datahub-gms" ))
• name: DATAHUB_GMS_PORT
value: "(f • Values.global.datahub. gms.port }) "
# Deprecated in favour of DATAHUB_* variables
• name: GMS_HOST
value: ff printf
"AS-$s" .Release.Name "datahub-gms" })
• name: GMS_ PORT
value: "({.Values.global.datahub.gms.port }]"
f
famous-florist-7218
08/03/2022, 4:16 AMCould you get the container log in
datahub-acryl-datahub-actions Copy code
kubectl logs << pod_name >> -c acryl-datahub-actionsl
little-breakfast-38102
08/03/2022, 4:52 AMHere is the log message
2022/08/01 222256 Waiting for:
http//health
2032/99022, 32-32 38, 28135 P,
dotan'tiP:"éfeal"bet"hittp://
eath":nttpinoHost in request UfL.
Steeping 15
l
little-megabyte-1074
08/04/2022, 8:00 PM
Hi @little-breakfast-38102! Gentle reminder to follow our Slack Guidelines & to please post large blocks of code in threads - it’s a HUGE help for us to keep track of open questions across our support channels!
i
incalculable-ocean-74010
08/11/2022, 9:17 AMCould you please do a kubectl describe of the failing pod and post the output here?
l
little-breakfast-38102
08/12/2022, 5:48 AM@incalculable-ocean-74010 this issue resolved after manually deleting replicas which persisted old variables. Thanks!
2 Views