# doPermissionsMigration: The role was not valid after upgrade to release-11.6
**URL:** https://forum.mattermost.com/t/dopermissionsmigration-the-role-was-not-valid-after-upgrade-to-release-11-6/25876
**Category:** Upgrade
**Created:** [May 13, 2026, 1:39pm UTC](https://forum.mattermost.com/t/dopermissionsmigration-the-role-was-not-valid-after-upgrade-to-release-11-6/25876 "2026-05-13T13:39:03Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@fooflington](https://forum.mattermost.com/u/fooflington)
#### Post date: [May 13, 2026, 1:39pm UTC](https://forum.mattermost.com/t/dopermissionsmigration-the-role-was-not-valid-after-upgrade-to-release-11-6/25876/1 "2026-05-13T13:39:04Z")
I’m running Mattermost Team edition within Docker and have been tracking `release-11` until today when watchtower did an upgrade to 11.6 and the service stopped starting. This is a relatively new install (about 3 weeks) so shouldn’t have too much “legacy” stuff knocking around.
The fatal error being logged is:
```json
{"timestamp":"2026-05-13 13:06:45.815 Z","level":"fatal","msg":"Failed to run app migration","caller":"app/migrations.go:882","migration":"Permissions Migrations","error":"doPermissionsMigration: The role was not valid., invalid input: entity: Role field: value: &{3uxwdr8h53fumrrnwk755cf1tc system_admin authentication.roles.global_admin.name authentication.roles.global_admin.description 1776157497755 1776498735184 0 [manage_others_outgoing_webhooks sysconsole_read_site_announcement_banner join_private_teams create_elasticsearch_post_indexing_job sysconsole_read_authentication_ldap order_bookmark_private_channel sysconsole_read_authentication_openid playbook_private_view manage_team_access_rules sysconsole_write_user_management_teams edit_post sysconsole_read_compliance_data_retention_policy delete_bookmark_private_channel manage_license_information create_group_channel sysconsole_read_integrations_bot_accounts use_group_mentions manage_others_bots manage_private_channel_banner manage_ldap_sync_job read_license_information sysconsole_read_environment_mobile_security sysconsole_read_experimental_features sysconsole_write_site_users_and_teams delete_private_channel sysconsol..."}
```
I’ve downgraded to `release-11.5` and it’s starting up ok now.
I’m using the pattern described in [Deploy Mattermost using Containers - Mattermost documentation](https://docs.mattermost.com/deployment-guide/server/deploy-containers.html) using Docker without a Proxy (I have Caddy in place instead).
- Postgres 18 (Alpine) as per Docker deployment guide
- Running within an Alpine 3.23 VM on x86\_64
- Working image: `mattermost/mattermost-team-edition:release-11.5` `afb9ff161421`
- Broken image: `mattermost/mattermost-team-edition:release-11` `34495e89ac5c`
Any hints…?
---
### Author:  [@jesse](https://forum.mattermost.com/u/jesse)
#### Post date: [May 15, 2026, 2:10pm UTC](https://forum.mattermost.com/t/dopermissionsmigration-the-role-was-not-valid-after-upgrade-to-release-11-6/25876/2 "2026-05-15T14:10:09Z")
Thanks for the report, @fooflington! I’ve replied to your post on [Mattermost](https://community.mattermost.com/core/pl/xhxerwuiebratjyy3n7by7rcgh) with a follow up, namely a hope you can help us root cause what went wrong by sharing this from your instance:
```sql
SELECT name, permissions FROM roles WHERE name = 'system_admin';
```
I’ve filed [Jira](https://mattermost.atlassian.net/browse/MM-68818) to track next steps once we know more.
---
### Author:  [@fooflington](https://forum.mattermost.com/u/fooflington)
#### Post date: [May 18, 2026, 9:04am UTC](https://forum.mattermost.com/t/dopermissionsmigration-the-role-was-not-valid-after-upgrade-to-release-11-6/25876/3 "2026-05-18T09:04:10Z")
This was sorted via MatterMost Community and is reportedly an issue with downgrade compatability issues. It was fixed by upgrading to `release-11.7`
With thanks to @jesse for his help!