Check for more duplicate issues during import from 1.6

[PaulStovell]

I think we made machine or environment use a UniqueConstraint and we aren't doing the same check during the import, so we can't report which one has the issue.

http://octopus-deploy.tenderapp.com/discussions/problems/16388-import-of-a-16-to-221-instance-produces-this-error-ensure-unique-constraint-violated-for-fields-versionbyproject

[PaulStovell]

Some improvements will be in 2.3

[dotnetwise]

Still same error with no clues whatsoever in 2.3

[nblumhardt]

@dotnetwise thanks for the heads-up. Can you possibly send your import log to support@ so we can dig in further?

[willfalconer]

This error is preventing us from completing our upgrade to 2.3. Happy to provide log and DB backups if we can find a resolution to this issue.

Will.

[dotnetwise]

We dropped all the releases in 1.6 by applying a retention policy of max 1 day.
Then we could import it.

However that also means we lost all the old releases but we didn't care that much about them.

That happened because from teamcity you could redeploy the same version multiple times.
On Octopus that showed as 1234, 1234_1, 1234_2 and so on. But during import they caused the process to fail.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.