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.

Sign up for GitHub

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

Jump to bottom

Migrations are timing out in 3.1 #2021

Closed
tothegills opened this issue Sep 23, 2015 · 3 comments
Closed

Migrations are timing out in 3.1 #2021

tothegills opened this issue Sep 23, 2015 · 3 comments
Assignees
@michaelnoonan
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
Milestone
3.1.2

Comments

@tothegills
Copy link
Contributor

Had a customer whose Add DeployedBy id column migration took 24 minutes so the transaction timed out and the migration happened again and again.

See: http://help.octopusdeploy.com/discussions/problems/39220-upgrade-to-31-sql-issue-killing-octopus-deploy-service
@tothegills tothegills added kind/bug This issue represents a verified problem we are committed to solving and removed kind/bug This issue represents a verified problem we are committed to solving labels Sep 23, 2015
@vanessalove vanessalove added priority (obsolete) This issue has been recognised as a priority and should be addressed as soon as possible this-week labels Sep 23, 2015
@michaelnoonan
Copy link
Contributor

Another source: http://help.octopusdeploy.com/discussions/problems/39422-octopus-server-3024-311-database-upgrade-failed

@michaelnoonan michaelnoonan changed the title Migrations are timing out in 3.1 Database Upgrade Scripts are timing out in 3.1 Sep 25, 2015
@michaelnoonan michaelnoonan changed the title Database Upgrade Scripts are timing out in 3.1 Migrations are timing out in 3.1 Sep 25, 2015
@michaelnoonan
Copy link
Contributor

Release Note: Allow the database upgrade script that added the DeployedBy column to be run multiple times as a workaround for some customers. Also increased the database operation timeout to the maximum to allow more time for these scripts to succeed.

@michaelnoonan michaelnoonan self-assigned this Sep 25, 2015
@MJRichardson MJRichardson added this to the 3.1.2 milestone Sep 27, 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.
Assignees

@michaelnoonan michaelnoonan

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
Milestone
3.1.2
Development

No branches or pull requests
5 participants
@MJRichardson @tothegills @hnrkndrssn @michaelnoonan @vanessalove