Closed Bug 736636 Opened 13 years ago Closed 13 years ago

Taskboard migrations don't work from scratch

Categories

(Participation Infrastructure :: Phonebook, defect)

Product:
Participation Infrastructure
Component:
Phonebook
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: tallOwen, Assigned: tofumatt)

References

Details

(Whiteboard: [re:03/21/2012][qa-])

If you start with a fresh database and run ./manage.py syncdb and ./manage.py migrate you end up with a bad task board database. At this point I think we should scrapping our migrations in task board and starting over.
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [re:03/21/2012]
Is this recent? The vagrant up still worked fine as of a few days ago. Wouldn't this cause the tests to fail too?
Not necessarily. Jenkins only runs new migrations.
Hm, if it's just the initial migration being broken, then you can fix that one manually.
I'm checking it out! huzzah!
Status: NEW → ASSIGNED
Assignee: timw → tofumatt
This happened because some old migrations were merged in when they shouldn't have been. Pull request forthcoming.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: mozillians.org → Phonebook
Product: Websites → Community Tools
QA Contact: mozillians-org → phonebook
Version: unspecified → other
Whiteboard: [re:03/21/2012] → [re:03/21/2012][qa-]
Bumping verified per irc conversation and [qa-]
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.