When trying to upgrade from 1.0.5 to 1.0.6… I get the following error:
[root@akiva migrations]# sudo -u awx /opt/awx/bin/awx-manage migrate
Traceback (most recent call last):
File “/opt/awx/bin/awx-manage”, line 11, in
sys.exit(manage())
File “/opt/awx/embedded/lib/python2.7/site-packages/awx/init.py”, line 109, in manage
execute_from_command_line(sys.argv)
File “/opt/awx/embedded/lib64/python2.7/site-packages/django/core/management/init.py”, line 364, in execute_from_command_line
utility.execute()
File “/opt/awx/embedded/lib64/python2.7/site-packages/django/core/management/init.py”, line 356, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File “/opt/awx/embedded/lib64/python2.7/site-packages/django/core/management/base.py”, line 283, in run_from_argv
self.execute(*args, **cmd_options)
File “/opt/awx/embedded/lib64/python2.7/site-packages/django/core/management/base.py”, line 330, in execute
output = self.handle(*args, **options)
File “/opt/awx/embedded/lib64/python2.7/site-packages/django/core/management/commands/migrate.py”, line 86, in handle
executor.loader.check_consistent_history(connection)
File “/opt/awx/embedded/lib64/python2.7/site-packages/django/db/migrations/loader.py”, line 298, in check_consistent_history
connection.alias,
django.db.migrations.exceptions.InconsistentMigrationHistory: Migration network_ui.0001_initial is applied before its dependency main.0027_v33
0_emitted_events on database ‘default’.
This is using the RPMs that I created… so this might be a bug in packaging… but to me it seems like an upgrade issue???
Upgrades between AWX versions are not expected to work. However, we have recently added an import/export capability to tower-cli/awx-cli, which allows you to export your job templates and other objects (not including credential secrets) to a JSON file, which you can then re-import to a freshly installed 1.0.6.
This (the awx-cli) is definitely not the best upgrade path right now… as far as I can see i’m loosing:
Users (export is blank), and therefore user permissions
Log/History
Inventory Groups
Credential passwords
LDAP/Auth config
Would be easier if the migration stuff would work… :)… It was working for all of the 1.0.5.* releases… expect of 1.0.5.31-1.0.5.32…
I don’t know ANYTHING about Django/DB stuff… But is it really that much more effort, to write it so that it’s at least migratable from the last minor??? (asking, not critisising)
Upgrades between AWX versions are not expected to work. However, we have recently added an import/export capability to tower-cli/awx-cli, which allows you to export your job templates and other objects (not including credential secrets) to a JSON file, which you can then re-import to a freshly installed 1.0.6.
It would also be nice if the “Ansible_Tower” modules at http://docs.ansible.com/ansible/latest/modules/list_of_web_infrastructure_modules.html could receive a bit of love and be extended to being able to fully configure an AWX instance/access all API objects. That way one could store the configuration for AWX in an Ansible role, throw away the old installation and configure the fresh, new one instead of dealing with some exported JSON files…
Feels a bit weird to have a server for a configuration management software resort to some custom process for configuration.