Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 3593 by michal.e...@gmail.com: Upgrade from 2.0.6 to 2.0.8 fails due to creation of index that already exists
https://code.google.com/p/reviewboard/issues/detail?id=3593

*** READ THIS BEFORE POSTING!
***
*** You must complete this form in its entirety, or your bug report will be
*** rejected.
***
*** If you have a security issue to report, please send it confidentially
to
*** secur...@reviewboard.org. Posting security-related issues to this bug
*** tracker causes us to have to do an emergency release.
***
*** For customer support, please post to reviewbo...@googlegroups.com
***
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** This bug tracker is public. Please check that any logs or other
information
*** that you include has been stripped of confidential information.


What version are you running?
2.0.6

What's the URL of the page containing the problem?
no url related problem

What steps will reproduce the problem?
1. Install rb 2.0.6.
2. Add two repositories
3. Upgrade to 2.0.8.

What is the expected output? What do you see instead?
upgrade should succeed, but it fails with a message saying that it cannot create index which already exists - scmtools_repository_8c446842.

What operating system are you using? What browser?
Ubuntu 14.04 LTS
DB on PostgreSQL

Please provide any additional information below.
Please verify upgrade scripts.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.

Reply via email to