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

migrations of data set table are failing #757

Closed
ngehlenborg opened this issue Oct 25, 2015 · 1 comment
Closed

migrations of data set table are failing #757

ngehlenborg opened this issue Oct 25, 2015 · 1 comment

Comments

@ngehlenborg
Copy link
Contributor

I am unable to update the VM with the latest code due to fab vm update failing during the application of migrations:

[vagrant@127.0.0.1:2200] out: 2015-10-25 15:37:01 DEBUG    south:270 execute() - execute "ALTER TABLE "core_workflowengine" ADD CONSTRAINT "core_workflowengine_slug_uniq" UNIQUE ("slug")" with params "[]"
[vagrant@127.0.0.1:2200] out: 2015-10-25 15:37:01 DEBUG    south:270 execute() - execute "ALTER TABLE "core_noderelationship" ADD CONSTRAINT "core_noderelationship_slug_uniq" UNIQUE ("slug")" with params "[]"
[vagrant@127.0.0.1:2200] out: 2015-10-25 15:37:01 DEBUG    south:270 execute() - execute "ALTER TABLE "core_dataset" ADD CONSTRAINT "core_dataset_slug_uniq" UNIQUE ("slug")" with params "[]"
[vagrant@127.0.0.1:2200] out: FATAL ERROR - The following SQL query failed: ALTER TABLE "core_dataset" ADD CONSTRAINT "core_dataset_slug_uniq" UNIQUE ("slug")
[vagrant@127.0.0.1:2200] out: The error was: could not create unique index "core_dataset_slug_uniq"
[vagrant@127.0.0.1:2200] out: DETAIL:  Key (slug)=() is duplicated.
[vagrant@127.0.0.1:2200] out: 
[vagrant@127.0.0.1:2200] out: Error in migration: core:0042_auto__add_unique_diskquota_slug__add_unique_download_slug__add_unique_
[vagrant@127.0.0.1:2200] out: IntegrityError: could not create unique index "core_dataset_slug_uniq"
[vagrant@127.0.0.1:2200] out: DETAIL:  Key (slug)=() is duplicated.
[vagrant@127.0.0.1:2200] out: 

Fatal error: run() received nonzero return code 1 while executing!

Requested: /vagrant/refinery/manage.py syncdb --migrate
Executed: /bin/bash -l -c "workon refinery-platform && /vagrant/refinery/manage.py syncdb --migrate"

Aborting.
Disconnecting from 127.0.0.1:2200... done.

screen shot 2015-10-25 at 2 35 56 pm

@ngehlenborg
Copy link
Contributor Author

The problem was that my database contained 3 datasets that had an empty string "" as their slug rather than (none). Those were data sets that were imported with the ISA-Tab UI upload rather than through the command line importer. I will investigate this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants