-
-
Notifications
You must be signed in to change notification settings - Fork 995
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blueprint error after migration from 2023.10.4 to 2024.2.1 #8681
Comments
Same type of error here: worker_1 | {"domain_url": null, "entry": "BlueprintEntry(model='authentik_brands.brand', state=<BlueprintEntryDesiredState.CREATED: 'created'>, conditions=[], identifiers={'domain': 'authentik-default', 'default': True}, attrs={'flow_authentication': <authentik.blueprints.v1.common.Find object at 0x7fd05120f200>, 'flow_invalidation': <authentik.blueprints.v1.common.Find object at 0x7fd05120cf80>, 'flow_user_settings': <authentik.blueprints.v1.common.Find object at 0x7fd05120f260>}, id=None, _state=BlueprintEntryState(instance=None))", "error": "EntryInvalidError("Serializer errors {'default': [ErrorDetail(string='Only a single brand can be set as default.', code='invalid')]}")", "event": "entry invalid: Serializer errors {'default': [ErrorDetail(string='Only a single brand can be set as default.', code='invalid')]}", "level": "warning", "log_level": "warning", "logger": "authentik.blueprints.v1.importer", "pid": 41748, "schema_name": "public", "task_id": "task-52aa6d281fa142a1820ade6296925445", "timestamp": "2024-02-24T08:07:36.606899"} |
I am also seeing this. I ran the sql mentioned by @vherrlein and I only have one brand as well. |
Actually, I just fixed mine. If you go to your brand and disable it as the default brand, save, then refresh. A new default authentic brand appears. Then you can disable it as the default and re-enable your custom brand as the default. |
Unfortunately it doesn’t work for me |
@vherrlein after disabling your custom brand as default, you'll need to ensure the task is re-ran as the next step. Head to Once done there, just navigate back to the Brands page, toggle default for the newly created |
@teambvd it worked like a charm. |
@vherrlein glad to hear it, and happy to help! Hopefully @rissson (or other) can pin this issue or something - I imagine pretty much anyone who's done anything to customize the look and feel of their install is going to see this (however many hundreds/thousands mightve watched the branding walkthrough someone did on YT a year or more back for example lol) |
This shouldn't really be related to the upgrade and more related to the brand blueprint running. We'll change the default brand blueprint to only attempt to set |
fixed by #9222 |
Describe the bug
Blueprint error after migration from 2023.10.4 to 2024.2.
entry invalid: Serializer errors {'default': [ErrorDetail(string='Only a single brand can be set as default.', code='invalid')]}
To Reproduce
Having a single customized Brand as default before doing the migration.
Expected behavior
Having status Successfull
Screenshots
Logs
Log output from the worker pod.
Version and Deployment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: