Upgrade to v5 (from v4) failing with 502 Bad Gateway

[gruga]

After the upgrade from v4 to v5, we're stuck with 502 BAD GATEWAY.
Last line on veeam log is:
Entity Framework Core 6.0.12 initialized 'VeeamAzureContext' using provider 'Npgsql.EntityFrameworkCore.PostgreSQL:6.0.8+e68dfe8b5cbe4a26d20acc36def6187aa1cfdda3' with options: MigrationsAssembly=Veeam.Azure.Data.Postgres.Migrations

Any ideas to how handle it?
Rollback is possible, but we would like to update to v5 for other issue.

[nielsengelen]

Hi Giorgio,

This looks like a technical issue, did you already contact support for assistance?

[gruga]

Yes, only a useless workaround for now

[nielsengelen]

Can you please share the case ID for future reference so we can look into it? If you are already in contact with them, then it's best to continue working with support as this is not a support forum and we may overlap with their actions/next steps.

[gruga]

Case #06018606
Last provided workaround: rollback
Just wanna know if someone else run in this issue

[nielsengelen]

I am not aware of someone with the specific same issue.

You can also use the Configuration Backup to create an extra backup on a repository. This way, you could deploy a fresh v5 and import everything from v4 in case the upgrade would keep failing.