ak server stuck in migration Applying authentik_core.0029_provider_backchannel_applications_and_more... #9866
Comments
|
I can reproduce that |
|
The error can be bypassed when adding Every change to the django.db.utils.ProgrammingError: relation "authentik_outposts_dockerserviceconnection" does not exist
LINE 1: ...ntik_outposts_dockerserviceconnection"."tls" FROM "authentik... |
|
The docker error is thrown by |
|
@EdungDivinefavour the version https://github.com/goauthentik/authentik/tree/version-2024.4 is working |
|
I'm seeing the same issue when bootstrapping a completely fresh instance of My ## Globally shared configuration for authentik components.
global:
# Default image used by all authentik components. For GeoIP configuration, see the geoip values below.
image:
# -- Overrides the global authentik whose default is the chart appVersion
tag: 2024.6.0
# -- If defined, an image digest applied to all authentik deployments
volumeMounts:
- mountPath: /media
name: media
volumes:
- name: media
persistentVolumeClaim:
claimName: authentik-media
storageClass: longhorn
size: 100m
env:
- name: AUTHENTIK_POSTGRESQL__USER
valueFrom:
secretKeyRef:
name: authentik-database-app-user
key: username
- name: AUTHENTIK_POSTGRESQL__PASSWORD
valueFrom:
secretKeyRef:
name: authentik-database-app-user
key: password
- name: AUTHENTIK_POSTGRESQL__READ_REPLICAS__0__USER
valueFrom:
secretKeyRef:
name: authentik-database-app-user
key: username
- name: AUTHENTIK_POSTGRESQL__READ_REPLICAS__0__PASSWORD
valueFrom:
secretKeyRef:
name: authentik-database-app-user
key: password
- name: AUTHENTIK_LOG_LEVEL
value: debug
envFrom:
- configMapRef:
name: authentik-env-variables
- secretRef:
name: authentik-credentials
## Authentik configuration
authentik:
# -- Log level for server and worker
log_level: info
# -- Secret key used for cookie singing and unique user IDs,
# don't change this after the first install
secret_key: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
## authentik server
server:
# -- The number of server pods to run
replicas: 2
# -- Init containers to add to the authentik server pod
## Note: Supports use of custom Helm templates
initContainers:
volume-permissions:
name: volume-permissions
image: busybox
command: ["sh", "-c", "chown -R 1000:1000 /media"]
volumeMounts:
- name: media
mountPath: /media
# -- Labels to be added to the authentik server pods
podLabels:
app.kubernetes.io/service: authentik-server
## authentik worker
worker:
# -- The number of worker pods to run
replicas: 2
# -- Labels to be added to the authentik worker pods
podLabels:
app.kubernetes.io/service: authentik-worker |
|
I was able to get the migrations to finish by editing the ...
outposts:
container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
disable_embedded_outpost: false
postgresql:
# read_replicas:
# '0': {}
user: postgres
host: localhost
...The error seems to be caused by the I'm not sure where the best place to fix this is since its technically a 'user error' by supplying an invalid config. But it took quite a while for me to locate the problem, so it might be a good idea to at least do some more validation on the |
Describe the bug
I followed all the steps in the Authentik full development setup here, and when I run ak serve, it runs forever and seems to get stuck In the step authentik_core.0029_provider_backchannel_applications_and_more...
To Reproduce
Follow the steps in the documentation, ensure to use the docker-compose.yml from the scripts folder as mentioned in the documentation
Run
ak serverExpected behavior
I expect the server to start running without any issues
Logs
Version and Deployment (please complete the following information):
Docker compose
Docker postgres logs
The text was updated successfully, but these errors were encountered: