dist-upgrade update failure

Bug #1560693 reported by Brad Figg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Blake Rouse
1.9
Fix Released
Critical
Newell Jensen

Bug Description

 > maasserver:0188_dli_power_driver_system_id_to_outlet_id
Error in migration: maasserver:0188_dli_power_driver_system_id_to_outlet_id
Traceback (most recent call last):
  File "/usr/sbin/maas-region-admin", line 68, in <module>
    main()
  File "/usr/sbin/maas-region-admin", line 64, in main
    run()
  File "/usr/sbin/maas-region-admin", line 57, in run
    management.execute_from_command_line()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/dist-packages/south/management/commands/migrate.py", line 107, in handle
    ignore_ghosts = ignore_ghosts,
  File "/usr/lib/python2.7/dist-packages/south/migration/__init__.py", line 219, in migrate_app
    success = migrator.migrate_many(target, workplan, database)
  File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 235, in migrate_many
    result = migrator.__class__.migrate_many(migrator, target, migrations, database)
  File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 310, in migrate_many
    result = self.migrate(migration, database)
  File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 133, in migrate
    result = self.run(migration)
  File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 107, in run
    return self.run_migration(migration)
  File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 81, in run_migration
    migration_function()
  File "/usr/lib/python2.7/dist-packages/south/migration/migrators.py", line 57, in <lambda>
    return (lambda: direction(orm))
  File "/usr/lib/python2.7/dist-packages/maasserver/migrations/0188_dli_power_driver_system_id_to_outlet_id.py", line 16, in forwards
    node.save()
  File "/usr/lib/python2.7/dist-packages/django/db/models/base.py", line 545, in save
    force_update=force_update, update_fields=update_fields)
  File "/usr/lib/python2.7/dist-packages/django/db/models/base.py", line 573, in save_base
    updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
  File "/usr/lib/python2.7/dist-packages/django/db/models/base.py", line 635, in _save_table
    forced_update)
  File "/usr/lib/python2.7/dist-packages/django/db/models/base.py", line 679, in _do_update
    return filtered._update(values) > 0
  File "/usr/lib/python2.7/dist-packages/django/db/models/query.py", line 507, in _update
    return query.get_compiler(self.db).execute_sql(None)
  File "/usr/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", line 975, in execute_sql
    cursor = super(SQLUpdateCompiler, self).execute_sql(result_type)
  File "/usr/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", line 781, in execute_sql
    cursor.execute(sql, params)
  File "/usr/lib/python2.7/dist-packages/django/db/backends/util.py", line 53, in execute
    return self.cursor.execute(sql, params)
  File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 99, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/lib/python2.7/dist-packages/django/db/backends/util.py", line 53, in execute
    return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: can't adapt type 'dict'

Related branches

Revision history for this message
Brad Figg (brad-figg) wrote :

I believe I was running MAAS version 1.8.2 prior to the attempted update. Looks like I was updating to maas-region-controller_1.9.1+bzr4543-0ubuntu1~trusty1_all.deb

Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Changed in maas:
assignee: nobody → Newell Jensen (newell-jensen)
Revision history for this message
Brad Figg (brad-figg) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote :
Changed in maas:
importance: Undecided → Critical
milestone: none → 1.9.2
status: New → Triaged
Revision history for this message
Newell Jensen (newell-jensen) wrote :

I have not been able to reproduce this with a new trusty VM and upgrading from MAAS 1.8.2 to MAAS 1.9 as you suggested. I also made sure I had a DLI machine in the database before doing sudo apt-get dist-upgrade. After a little googling for this error I found that others have ran into this problem:

https://code.djangoproject.com/ticket/23776

Brad, are yous till seeing this error when you go to do a dist-upgrade? If so, can you get me the logs for postgres?

Thanks

Revision history for this message
Newell Jensen (newell-jensen) wrote :

Brad,

I just refreshed my browser and have seen your maas-django.log and regiond.log

There are a lot of database errors in these files:

The MAAS database cannot be used. Please investigate: fe_sendauth: no password supplied

I didn't see any of these errors in my dist-upgrade so something funky happened here.

no longer affects: maas/2.0
Changed in maas:
milestone: 1.9.2 → 2.0.0
Changed in maas:
status: Triaged → In Progress
assignee: Newell Jensen (newell-jensen) → Blake Rouse (blake-rouse)
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
jdh239 (jdh239) wrote :

I don't understand, based on the above, if this fix is set for 1.9.3 or and update for 1.9.3? If so, what would be the ETA for the fix?

Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.