Closed abarciauskas-bgse closed 1 year ago
@abarciauskas-bgse if you have kubectl installed could you ran the following:
kubectl get pods --namespace=dev keycloak-0
, this will tell if Keycloak is runningkubectl describe pod -n dev keycloak-0
, will show the pod's eventskubectl logs -n dev keycloak-0 --tail 100
will give us some logsalso, have you tried running the deploy command after a few minutes passed since the first timeout error?
Hi @abarciauskas-bgse, we released v0.4.5
Friday. This latest release should resolve the issues you're experiencing above. Thank you for your interest in QHub and let us if your deployment was successful :)
Adding @tracetechnical to this thread - he has been troubleshooting our deployment and found and fixed the issue with EBS CSI drivers and the updated kubernetes version, so we do believe the 0.4.5 upgrade should fix this problem. Thanks @iameskild
@abarciauskas-bgse @tracetechnical wonderful! We also fixed the EBS CSI driver issue in this latest release so it sounds like we're in good shape. Unless there is anything else, at this point, I think we can close this issue.
OS system and architecture in which you are running QHub
macOS Catalina 10.15.7
Expected behavior
Successful deployment of stage 05-kubernetes-keycloak
Actual behavior
Upon repeat deployments, I am getting this error:
from this change:
How to Reproduce the problem?
This is my config:
so with GITHUBTOKEN, AWS creds set, I run the
qhub deploy -c aimee-config.yaml
Command output
No response
Versions and dependencies used.
Others that might be relevant:
Compute environment
AWS
Integrations
Keycloak
Anything else?
No response