Exception in thread "main" java.io.IOException: Invalid keystore format #92
Comments
|
What are the logs from the |
|
|
odd, there should be some output. what method did you use for install? ouctl? |
|
ouctl yes |
|
Ok redeployed and i see this: (secret yaml content above) hecking static key lastmile-oidc QMEAgEFAAQgV+7prN0tVPLHI3p1pdrsSurqVikq6c0Si4iHGFjQWoYEFE6DS9oJfds3SFEzTtC9y/NZbrpcAgInEA=="},"kind":"Secret","type":"Opqaue"} |
|
odd, what version of Kubernetes and what distrobution (ie kubeadmin, EKS, etc)? Also, list out the |
|
k0s is the distro, https://docs.k0sproject.io/ Client Version: v1.28.0 k0s version kubectl get secret -n openunison Thanks again Marc |
|
everything looks OK there. I don't think this would do it but If that doesn't do it, can you run |
|
Failed the same with saml2 |
|
I wonder what you expect here: k0s sets the kubelet under this path |
|
Odd. This usually happens when the API server gets "confused" about Does it come back as |
|
kubectl get secret orchestra -n openunison -o json | jq -r '.data["ou.env"]' | base64 -d | grep myvd |
|
i'll see if i can reproduce. there's nothing really strange going on here but i've never tried on k0s before. |
|
thx |
|
so i took your values.yaml, deployed it onto k0s with just different host names and ldap connection info and it worked perfectly. Can you please provide the part of the logs from the beginning og the container? tere shouldn't be anything sensitive. |
|
Ok : I waited on night and the cronjob was executed i think ok , but the pods are still failing
here is the full log |
|
everything looks normal. try setting |
java.io.IOException: keystore password was incorrect - Which password? |
|
Ok, i found it - thx a lot the secret file that is not a k8s should no longer have K8S_DB_SECRET and unisonKeystorePassword. Can you please update the documentation if you feel necessary on how that secret should look like should only be Again thanks a lot |
|
Now - myabe I open a new ticket? I dont have the oicd flags enabled on k0s so i chose Is it normal to have that pod stuck in creating Later edit: I am authorized by AD but still the pod stuck in creating |
|
that's odd. the |
|
When I do the install I use |
|
Hello, I got the problem, in my case it was password character fault. Using password with special character give me the same error. Change for password with letter and '_' only work. Don't know with character are in fault. |
|
Ok So i was able to do 3 times the deployments and it worked. I notice though another strange behavior. If dashboard was deployed before open unison there is an issue with untrusted certificate DN (Empty issuer DN not allowed in X509Certificates) |
Hello,
I am trying to install openunison on top of k0s .
looks like whatever parameters i chose i always hit this issue
Exception in thread "main" java.io.IOException: Invalid keystore format
Can you please advice what should i do to have openunison working with LDAP connector (i dont have any oidc flags on on the k0s )
I am using nginx ingress controller whee i terminate TLS with a valid and trusted certificate
Then this is the pod crashing log
The text was updated successfully, but these errors were encountered: