Unexpected upgrade history detected during migration from Server to Container

Octopus Server
1

I’m trying to migrate from Octopus Windows Server v2023.2 (Build 9088-hotfix.9778) - which I got to match the Cloud version to allow a project export/import and now to Octopus Container octopusdeploy/octopusdeploy:2023.1.10597 which is the latest container version

I’m seeing the following error during task start up:

Checking database schema upgrade history...
Database upgrade "abandoned" after 431ms

Unexpected upgrade history detected. You probably need to upgrade to a later version of Octopus Server. Extra upgrade script(s) found: Script0374RemoveTypesFromHealthCheckServerTasks, Script0375CreateKubernetesTaskResourceStatusTable, Script0375RemoveMachineHealthCheck, Script0376RemoveInsightsFeaturesConfiguration

Octopus.Shared.ControlledFailureException: Unexpected upgrade history detected. You probably need to upgrade to a later version of Octopus Server. Extra upgrade script(s) found: Script0374RemoveTypesFromHealthCheckServerTasks, Script0375CreateKubernetesTaskResourceStatusTable, Script0375RemoveMachineHealthCheck, Script0376RemoveInsightsFeaturesConfiguration

Clearly this is due to the version mismatch, but the container version is lagging far behind server and cloud. Do you expect to rev the published container version to one that would match the hotfix version I have?

Sincerely
Pete

3

Hi @peter_m_mcevoy,

Thanks for reaching out, I’d be happy to help with getting your server instance that is on 2023.2 migrated to a container!

Do you expect to rev the published container version to one that would match the hotfix version I have?

Our docker hub images follow our general on-prem release so 2023.2 should be coming very soon but we do have another repository for images that are being tested.

You should be able to use the following image:
docker.packages.octopushq.com/octopusdeploy/octopusdeploy:2023.2.9088-hotfix.9778

Hope that helps, feel free to reach out with any questions or issues at all!

Best Regards,

4

Brilliant! that worked a treat :slight_smile:

(although I now have other issues on startup, but that’s with me - I think I’m not giving the server enough time to start…)

Regarding the approriate time for me to swap from the “hotfix” channel, to the main release channel on docker hub, do I just need to wait for a version higher than 2023.2.9088? Will that upgrade from the hotfix?

Pete

5

That’s correct, once 2023.2 is fully released, which we’re hoping will be within the next week or so, the available container version will be a build higher than the hotfix allowing you to upgrade.

6

Thank you both for swift response and resolution.

Pete

1 Like