Unable to Create Storage After Upgrading from Appwrite 1.8.0 to 1.9.0

We upgraded our Appwrite instance from version 1.8.0 to 1.9.0 and successfully ran the migration process. However, after the upgrade, we are no longer able to create new Storage buckets.

The issue started immediately after the update. Before upgrading, Storage creation was working without any problems.

Additionally, we could not find any official documentation regarding how to safely downgrade Appwrite from 1.9.0 back to 1.8.0. We would appreciate guidance on whether rollback/downgrade is supported and what the recommended process is.

Appwrite Version: 1.9.0 Previous Version: 1.8.0 Migration executed: Yes Deployment: Self-hosted / Docker

<@287294735054274560> Can you help with this?

<@287294735054274560> ?

Morning guys ☀️

Looking at code, transformation is new attribute, expected to be covered by migration: https://github.com/appwrite/appwrite/blob/54693d94178ed24893e6f4bdf0f8cac7d6eafa5d/src/Appwrite/Migration/Version/V23.php#L143-L150

Did you have any failures during migrations regarding this? From what I recall, migrations should be safe to re-run, so we can try now.

As for downgrading, sadly no docs around that. Instead, backup is recommended, before running migration. Providers like DigitalOcean or Hetzer often provide 1-click solution for this with ability to restore from backups into a new machine.

I didn't encounter any issues during the upgrade. I ran the migrate command again, but the problem persists. I don't have a backup for a downgrade, and my projects are now useless.

as a last thing, you can try creating the column manually on the differents MariaDB bucket tables : "ALTER TABLE Xbuckets ADD COLUMN transformations TINYINT(1) UNSIGNED NOT NULL DEFAULT 1;" (if i'm not wrong it's on all the _<iid>_buckets where iid is just an internal ID)

alter table _1_buckets add column transformations tinyint(1) unsigned not null default 1;

I did this for all the IDs, but the same error persists.

I added the following to the attributes inside the buckets row in the _id_metadata table:

{
  "$id": "transformations",
  "type": "boolean",
  "size": 0,
  "required": true,
  "signed": true,
  "array": false,
  "filters": [],
  "default": 1,
  "format": ""
}

After that, I ran the migration again, and the issue was fixed.