Update failed 9.3 -> 9.10

Status
Not open for further replies.

Meik

Cadet
Joined
Apr 25, 2016
Messages
3
After updating to 9.10 I got an error alert.

Update failed. Check /data/update.failed for further details.​

I already searched through the forum and found similar errors, but those were about NOT NULL constraint failed while my error is different (table already exists).

What should I do to resolve?

Regards
Meik

Code:
/data/update.failed:
FATAL ERROR - The following SQL query failed: CREATE TABLE "_south_new_storage_encrypteddisk" ("encrypted_volume_id" integer NOT NULL, "id" integer PRIMARY KEY, "encrypted_provider" varchar(120) NOT NULL UNIQUE, "encrypted_disk_id" varchar(100) NULL)
The error was: table "_south_new_storage_encrypteddisk" already exists
Running migrations for api:
- Nothing to migrate.
- Loading initial data for api.
Installed 0 object(s) from 0 fixture(s)
Running migrations for freeadmin:
- Nothing to migrate.
- Loading initial data for freeadmin.
Installed 0 object(s) from 0 fixture(s)
Running migrations for vcp:
- Nothing to migrate.
- Loading initial data for vcp.
Installed 0 object(s) from 0 fixture(s)
Running migrations for support:
- Nothing to migrate.
- Loading initial data for support.
Installed 0 object(s) from 0 fixture(s)
Running migrations for sharing:
- Nothing to migrate.
- Loading initial data for sharing.
Installed 0 object(s) from 0 fixture(s)
Running migrations for system:
- Nothing to migrate.
- Loading initial data for system.
Installed 0 object(s) from 0 fixture(s)
Running migrations for tasks:
- Nothing to migrate.
- Loading initial data for tasks.
Installed 0 object(s) from 0 fixture(s)
Running migrations for plugins:
- Nothing to migrate.
- Loading initial data for plugins.
Installed 0 object(s) from 0 fixture(s)
Running migrations for services:
- Nothing to migrate.
- Loading initial data for services.
Installed 0 object(s) from 0 fixture(s)
Running migrations for jails:
- Nothing to migrate.
- Loading initial data for jails.
Installed 0 object(s) from 0 fixture(s)
Running migrations for account:
- Nothing to migrate.
- Loading initial data for account.
Installed 0 object(s) from 0 fixture(s)
Running migrations for network:
- Nothing to migrate.
- Loading initial data for network.
Installed 0 object(s) from 0 fixture(s)
Running migrations for directoryservice:
- Nothing to migrate.
- Loading initial data for directoryservice.
Installed 0 object(s) from 0 fixture(s)
Running migrations for storage:
- Migrating forwards to 0059_encrypted_disk_id_null.
> storage:0057_migrate_disk_id_to_identifier
- Migration 'storage:0057_migrate_disk_id_to_identifier' is marked for no-dry-run.
! Error found during real run of migration! Aborting.

! Since you have a database that does not support running
! schema-altering statements in transactions, we have had
! to leave it in an interim state between migrations.

! You *might* be able to recover with:  (migration cannot be dry-run; cannot discover commands)
! The South developers regret this has happened, and would
! like to gently persuade you to consider a slightly
! easier-to-deal-with DBMS (one that supports DDL transactions)
! NOTE: The error which caused the migration to fail is further up.
Error in migration: storage:0057_migrate_disk_id_to_identifier
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/manage.py", line 42, in <module>
  execute_from_command_line(sys.argv)
  File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
  utility.execute()
  File "/usr/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
  self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
  self.execute(*args, **options.__dict__)
  File "/usr/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
  output = self.handle(*args, **options)
  File "/usr/local/lib/python2.7/site-packages/south/management/commands/migrate.py", line 111, in handle
  ignore_ghosts = ignore_ghosts,
  File "/usr/local/lib/python2.7/site-packages/south/migration/__init__.py", line 220, in migrate_app
  success = migrator.migrate_many(target, workplan, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 256, in migrate_many
  result = migrator.__class__.migrate_many(migrator, target, migrations, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 331, in migrate_many
  result = self.migrate(migration, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 133, in migrate
  result = self.run(migration, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 114, in run
  return self.run_migration(migration, database)
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 84, in run_migration
  migration_function()
  File "/usr/local/lib/python2.7/site-packages/south/migration/migrators.py", line 60, in <lambda>
  return (lambda: direction(orm))
  File "/usr/local/www/freenasUI/../freenasUI/storage/migrations/0057_migrate_disk_id_to_identifier.py", line 37, in forwards
  db.alter_column(u'storage_encrypteddisk', 'encrypted_disk_id', self.gf('django.db.models.fields.CharField')(max_length=100, null=True))
  File "/usr/local/lib/python2.7/site-packages/south/db/sqlite3.py", line 232, in alter_column
  name: self._column_sql_for_create(table_name, name, field, explicit_name),
  File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 47, in _cache_clear
  return func(self, table, *args, **opts)
  File "/usr/local/lib/python2.7/site-packages/south/db/sqlite3.py", line 110, in _remake_table
  ", ".join(["%s %s" % (self.quote_name(cname), ctype) for cname, ctype in definitions.items()]),
  File "/usr/local/lib/python2.7/site-packages/south/db/generic.py", line 282, in execute
  cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute
  return self.cursor.execute(sql, params)
  File "/usr/local/lib/python2.7/site-packages/django/db/utils.py", line 99, in __exit__
  six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute
  return self.cursor.execute(sql, params)
  File "/usr/local/www/freenasUI/../freenasUI/freeadmin/sqlite3_ha/base.py", line 372, in execute
  execute = Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: table "_south_new_storage_encrypteddisk" already exists
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
I'd file a bug report. When you do, please post the issue number here, for future reference.
 
D

dlavigne

Guest
That should have been fixed in the 201604181743 update. Do you know which update number failed?
 

Meik

Cadet
Joined
Apr 25, 2016
Messages
3
I upgraded to: FreeNAS-9.10-STABLE-201604181743 (74ef270) but the error remains.
I will create a bug this evening when I'm back from work.
 
Status
Not open for further replies.
Top