https://datahubproject.io logo
Join Slack
Powered by
Hi after upgrading to latest release the catalog i...
# troubleshoot
b
Hi after upgrading to latest release the catalog is not usable anymore as I am getting a lot of 
Validation error of type FieldUndefined: Field 'displayName' in type 'CorpUserEditableProperties' is undefined @ 'searchResults/searchResults/entity/editableProperties/displayName' (code undefined
errors. Anyone else facing this after the upgrade?
n
me too!
Copy code
Validation error of type FieldUndefined: Field 'displayName' in type 'CorpUserEditableProperties' is undefined @ 'me/corpUser/editableProperties/displayName' (code undefined)
solved after upgrading everything but the mysqlSetupJob and datahubUpgrade to the v0.8.27
l
@big-carpet-38439 @early-lamp-41924 ^
g
Hey @bland-orange-95847 did you upgrade your gms instance and your frontend? This looks like your frontend got ahead of your gms instance
b
I used the latest helm chart
And just did a helm upgrade
g
i see.. @early-lamp-41924 any ideas why the latest helm chart might not upgrade GMS?
e
Could you check the image version deployed to gms? Just to confirm that this is thecase
also just to confirm, do you explicitly set image tag in your values.yaml?
b
no, I do not overwrite image tags and just use the default ones. I already did a rollback
checked the helm history. interesting values I found were
Copy code
managed_ingestion:
        defaultCliVersion: 0.8.26.6

repository: linkedin/datahub-frontend-react
    tag: v0.8.27

repository: linkedin/datahub-gms
    tag: v0.8.27
e
what if you describe the deploy of these two things in kubernetes? 
kubectl describe deploy datahub-datahub-gms -n <<namespace>>
do you see that it correctly deployed v0.8.27?
b
just did a redeploy and yes deployments are both v0.8.27
but I saw that gms pod is not starting. Its missing 
"datahub-encryption-secrets"
is this something new?
e
ahhhh
what do you get when you run
Copy code
kubectl get secrets -n <<namespace>>
so the latest helm chart if https://github.com/acryldata/datahub-helm/blob/master/charts/datahub/values.yaml#L143 is not overriden should create this secret automatically
cc @big-carpet-38439
b
this secret was not automatically deployed, so its not there. Only 
datahub-gms-secret
besides some others
provisionSecret
and 
provisionSecrets
are set to true, so I guess there is something missing in the helm chart
e
it checks whether the secret exists and whether the above flag is set to true
b
datahub-auth-secrets
also wasn’t deployed. Could it be that it does not work for an upgrade?
ook no, the dry-run shows that it would create the secret.. that’s strange
and a second upgrade fixed it 🤯
so thank you for your support ❤️ in the end it just was a strange thing on my side 😕
e
Awesome! That’s very strange hmn wonder if it has something to do with the order of creation
b
Wonderful!
11 Views
Open in Slack
PreviousNext
Powered by