Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception migrating to 3.1 #1969

Closed
MJRichardson opened this issue Sep 3, 2015 · 2 comments
Closed

Exception migrating to 3.1 #1969

MJRichardson opened this issue Sep 3, 2015 · 2 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving priority (obsolete) This issue has been recognised as a priority and should be addressed as soon as possible

Comments

@MJRichardson
Copy link

An exception is being thrown when migrating from 2.6 -> 3.1
As reported in http://help.octopusdeploy.com/discussions/problems/38466-problem-importing-26-octobackup-to-30

@MJRichardson MJRichardson added kind/bug This issue represents a verified problem we are committed to solving priority (obsolete) This issue has been recognised as a priority and should be addressed as soon as possible this-week labels Sep 3, 2015
@michaelnoonan michaelnoonan self-assigned this Sep 5, 2015
@michaelnoonan michaelnoonan added this to the 3.1 milestone Sep 5, 2015
@michaelnoonan
Copy link
Contributor

Release Note: Fixed a bug that blocked the Migrator from starting correctly.

@michaelnoonan michaelnoonan modified the milestones: 3.1.0-beta0002, 3.1 Sep 10, 2015
@lock
Copy link

lock bot commented Nov 26, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving priority (obsolete) This issue has been recognised as a priority and should be addressed as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants