Closed zagr0 closed 2 years ago
the bad thing is that when I rollback to 0.25.6 I'm getting:
time=2022-11-02T14:39:17Z level=fatal msg=Could not ensure that signing keys for "hydra.openid.id-token" exists. If you are running against a persistent SQL database this is most likely because your "secrets.system" ("SECRETS_SYSTEM" environment variable) is not set or changed. When running with an SQL database backend you need to make sure that the secret is set and stays the same, unless when doing key rotation. This may also happen when you forget to run "hydra migrate sql".. audience=application error=map[message:unable to fetch records: sql: Scan error on column index 3, name "pk": converting driver.Value type string ("08eed7fe-68b3-47eb-8a46-94397d81e34d") to a int: invalid syntax] service_name=Ory Hydra service_version=v1.11.8
we use external secret to provide cookie and systems hydra secrets:
secret:
enabled: false
nameOverride: hydra-secrets
Another user had a similar problem and the root cause that they were running custom clean up jobs which caused this problem. To me it looks like this is the same problem
There's another user indicating that there is something for sure broken. Upstream issue is https://github.com/ory/hydra/issues/3346
Preflight checklist
Describe the bug
When you upgrade hydra helm chart deployment from 0.25.6 -> 0.26.0 the auto migration job fails with error:
Reproducing the bug
helm upgrade ory/hydra
from 0.25.6 to 0.26.0Relevant log output