Issue importing project from 2.5.8 to a test 2.6 environment via Octo.exe

I was following the instructions (https://octopusdeploy.com/blog/octo-exe-import-export) to export/import a project from our production Octopus Deploy environment running 2.5.8 to an internal environment running Octopus Deploy 2.6 to test the new lifecycles feature, and ran into the following issue when attempting to import:

===========================================
Octopus Deploy Command Line Tool, version 2.5.10.39

Handshaking with Octopus server: https://octopusdev
Handshake successful. Octopus version: 2.6.0.751; API version: 3.0.0
Finding importer 'project’
Beginning the import
Export file successfully loaded
Checking that all environments exist
Checking that all machines exist
Checking that all NuGet Feeds exist
Checking that all Library Variable Sets exist
Checking that the Project Group exist
Beginning import of project 'Demo2’
Importing Project
Project does not exist, a new project will be created
Error from Octopus server (HTTP 400): There was a problem with your request.

  • The project must be assigned to a lifecycle.

Exit code: -7

While not a showstopper for this test setup, I’m not sure how I would work around this error since Lifecycles was introduced in 2.6, but my exported projects came from an earlier release. Is there something I might be missing here?

Any information would be appreciated! Thanks for your great help and support!

-Sam

Hi Sam,

Thanks for getting in touch and sorry for the trouble. You’d need to upgrade the original server to 2.6, and then export it for use in the new server, though I can see that it breaks your test workflow. We’ll see if we can fix this in a newer version of Octo.exe.

Paul

Hi Paul,

I appreciate the reply. I actually uninstalled the 2.6 test environment,
installed 2.5 in its place, then imported the projects from production to
test successfully. I’m sure it will be fine upgrading test to 2.6 now.

Thank you again for your feedback!

Sam

Hi Paul,

Just as a follow-up, we upgraded our Production instance to 2.6 without issues, and attempted an export and import of another project from Production into our 2.6 Development instance. We again ran into the following error:
“Error from Octopus server (HTTP 400): There was a problem with your request. - The project must be assigned to a lifecycle.”

Is there another unlisted requirement that we may be overlooking?

Thanks,
Sam

Hi Sam,

Thanks for the follow up. I have created a GitHub issue for this to be fixed.
You can track it here: https://github.com/OctopusDeploy/Issues/issues/1421

I don’t think you are missing anything, it does appear it might have been overlooked.

Vanessa