https://datahubproject.io logo
Join Slack
Powered by
Hey Guys, I was using datahub v0.8.42 but was expe...
# troubleshoot
s
Hey Guys, I was using datahub v0.8.42 but was experiecing the issue reported here: https://github.com/datahub-project/datahub/issues/4854 It's supposed fixed in this version correct? But I am still having the "Sign Out" button redirect to the main page using Google OIDC. Anyone having the same problem?
I am getting the following logs:
Copy code
ERROR auth.sso.oidc.OidcCallbackLogic - Unable to renew the session. The session store may not support this feature
b
would you mind upgrading to the most recent version of datahub and trying that? I'm not sure if this issue was fixed in 0.8.42 or 0.8.43
the fact that you're redirecting to the homepage makes me believe it was in 0.8.43!
b
Release history suggests 0.8.42. Which Identity Provider are you using?
And can you confirm that you've updated your frontend image? Sometimes these can get out of sync
It says you're on v0.8.34 in your drop down. This is an older version!
s
@big-carpet-38439 The gif above is not me. I used it because it seems to be the same problem( at least in the behaviour side, because the solution in the thread didnt work for me), sorry the confusion. I'm using v0.8.42 I'm using Google OIDC. I set up a similar Oauth client for metabase and is running smoothly, so I don't thing is the Oauth client setup on Google is to blame here. The images I'm using are:
Copy code
IMAGE                                     COMMAND                  CREATED        STATUS                  PORTS                                                                                            NAMES
confluentinc/cp-schema-registry:5.4.0     "/etc/confluent/dock…"   21 hours ago   Up 21 hours             0.0.0.0:8081->8081/tcp, :::8081->8081/tcp                                                        schema-registry
confluentinc/cp-kafka:5.4.0               "/etc/confluent/dock…"   21 hours ago   Up 21 hours             0.0.0.0:9092->9092/tcp, :::9092->9092/tcp                                                        broker
acryldata/datahub-actions:head            "/bin/sh -c 'dockeri…"   21 hours ago   Up 21 hours                                                                                                              datahub-datahub-actions-1
linkedin/datahub-frontend-react:v0.8.42   "datahub-frontend/bi…"   21 hours ago   Up 21 hours (healthy)   0.0.0.0:9002->9002/tcp, :::9002->9002/tcp                                                        datahub-frontend-react
elasticsearch:7.9.3                       "/tini -- /usr/local…"   21 hours ago   Up 21 hours (healthy)   0.0.0.0:9200->9200/tcp, :::9200->9200/tcp, 9300/tcp                                              elasticsearch
neo4j:4.0.6                               "/sbin/tini -g -- /d…"   21 hours ago   Up 21 hours             0.0.0.0:7474->7474/tcp, :::7474->7474/tcp, 7473/tcp, 0.0.0.0:7687->7687/tcp, :::7687->7687/tcp   neo4j
confluentinc/cp-zookeeper:5.4.0           "/etc/confluent/dock…"   21 hours ago   Up 21 hours             2888/tcp, 0.0.0.0:2181->2181/tcp, :::2181->2181/tcp, 3888/tcp                                    zookeeper
linkedin/datahub-gms:v0.8.42              "/bin/sh -c /datahub…"   21 hours ago   Up 21 hours (healthy)   0.0.0.0:8080->8080/tcp, :::8080->8080/tcp                                                        datahub-gms
I was having some problems running the v0.8.43 so I downgrade to v0.8.42 . and ran 
datahub-upgrade.sh
script to restore the indices. Think it might have something to do with the problem?
7 Views
Open in Slack
PreviousNext
Powered by