-
Notifications
You must be signed in to change notification settings - Fork 66
New fabric8 4.x not starting properly (keycloak) #1185
Comments
same problem here after installing with gofabric8 |
👍 |
cc @sbose78 |
+1 |
+1 k8s : gofabric8 : |
We need to investigate why https://github.com/fabric8-apps/keycloak-app/blob/master/keycloak/src/main/fabric8/cm.yml#L18 is not showing up. |
@Secathor hello, have you figured out how to solve this Base64 problem ? i am trying to debug it, i reviewed the source codes, look like when decode, there is invalid char that causes this problem. |
@shuang-x-zhao-gj Nope, I'm currently still on "old" v2 fabric8. |
keycloak is trying to base64-decode the string "${KEYCLOAK_PRIVATEKEY}". |
But later on the login fails with: oauth2: cannot fetch token: 400 Bad Request Response: {"error":"unauthorized_client","error_description":"Invalid client secret"}?error and the keycloak log: |
I have made fabric8 and keycloak started on my K8s cluster, but i made some fixes/workarounds to make it run, but i still got other problem for keycloak... firstly, the replacement of ${KEYCLOAK_PRIVATEKEY} didn't happen in my env, i debugged it, the property wasn't replaced so the "$" was the first char read by base64 decode; i just hardcoded the public key and private key to proceed; then i met another problem of this private key, the decode told me the private key had extra data so the key was invalid, i had to generate new private key and public key myself to pass this problem then, i got fabric8 and keycloak to start, when i tried to log in fabric8 the first time, i got other problems, they were about keycloak itself or about DNS resolve between those fabric8 services, i got all fixed or workaround finally, i can login to keycloak as admin, then i created user, but i met a new problem when i tried to login to fabric8 with the new user (i also tried to grant permission by github sso, the same problem happened), the error looked like below: Post http://keycloak.fabric8.dev-platform.hillhousebootcamp.com/auth/realms/fabric8/protocol/openid-connect/token: dial tcp: lookup keycloak.fabric8.dev-platform.hillhousebootcamp.com on 10.96.0.10:53: read udp 10.244.2.65:45589->10.96.0.10:53: i/o timeout?error so here is the place i am stuck, i am trying to solve it now. |
@gwipplinger after i solved the dns look up problem, i am seeing the same problem as you do, have you figured out how to pass it ? |
@shuang-x-zhao-gj I'm sorry, I haven't made any progress on that either, and unfortunately I don't have time for the next few days. |
@gwipplinger hey, i checked into this a little, i see in the env of keycloak and auth pods, for the keycloak client (fabric8-online-platform) secret they have same value, but there is etc/config.yaml file inside auth pod, it has different value for keycloak.secret i suppose although the env has property point to one secret value, the service uses the value from etc/config.yaml, i am not sure about it, but it may be a clue for you to check BTW, i download the source of auth service, the config.yaml file is hardcoded... so i haven't find out a way to try my thought |
@shuang-x-zhao-gj i replaced in the keycloak configmap the secret: |
@gwipplinger yes, that's the way pass the problem, i used the same way. I also can log in to fabric console, i can grant by github, create workspace, import codebase and i create a pipeline but then nothing else works... the pipeline doesn't run when i commit/push codes, and i can not run "start pipeline" or "open in IDEA" from the console for my codebase, even if i browse my codebase details i get error "Your workspace failed to load"... i checked the source codes of fabric-ui, i got nothing till now. And as shown from the demo of fabric8 official page, there are some templates you can use to "quickstart" with new git repository, but in my case, i got nothing to choose, so this road also means nothing to me. Another problem is if i use firefox outside, some contents of the console can not correctly show up; but if i use firefox inside the master node, i can see them ... another strange thing... -Roger |
@Secathor hi, i am curious what version is "old" v2 fabric8? Could you share with me your docker version, k8s version and fabric8 version that working in your system ? |
+1
Issue was first created on Nov, 2017 and it hasn't been fixed yet. Could you please at least share a workaround so that anyone can start fabric8 on their local machine? As a developer who just want to test fabric8, this kind of an issue is really discouraging. |
+1 |
1 similar comment
+1 |
As Explained by this And init-containers are Tech Preview and not supported by OpenShift origin... Can anyone confirm this? |
I was able to run Keycloak by adding it in deployment yml for keycloak
|
+1 |
Hi !
I've some issues when trying latest fabric8 version 4.x.
Environment
Installation steps
Following new install procedure here.
Issue state
All seems to wait for Keycloak, here's the logs:
OK, adding config file as a volume like that on deployment
fabric8/keycloak
:Then keycloak logs look that now:
I don't know how to go further...
So, there's two issues in this ticket:
The text was updated successfully, but these errors were encountered: