Skip to content

Upgrading from 2024.3 or earlier directly to 2025.4+ is broken #10126

Description

@grace-rehn

Severity

Sev2 - Medium

Version

2024.3 or earlier to 2025.4+

Latest Version

I could reproduce the problem in the latest build

What happened?

2025.4+ released a change that relies on a migration script from 2024.3.4894 to have been executed which causes upgrade failures.

Reproduction

Create an instance before 2024.3.4894
Upgrade to latest

Error and Stacktrace

The Octopus server exited unexpectedly.
Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid column name 'DataVersion'.
Invalid column name 'LastModified'.
   at Microsoft.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__195_0(Task`1 result)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---

More Information

No response

Workaround

Upgrade to a version after 2024.3.4894 but before 2025.4.10666 and then to any later version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugThis issue represents a verified problem we are committed to solving

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions