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

[11.0 -> 12.0] Fail to migrate sale_layout_category_hide_detail #75

Closed
Danoolo opened this issue Nov 15, 2019 · 1 comment
Closed

[11.0 -> 12.0] Fail to migrate sale_layout_category_hide_detail #75

Danoolo opened this issue Nov 15, 2019 · 1 comment

Comments

@Danoolo
Copy link

Danoolo commented Nov 15, 2019

Hi guys!!...when trying to migrate a 11.0 db backup i found this error:

2019-11-15 21:52:19,662 32511 CRITICAL AP12.0a odoo.service.server: Failed to initialize database AP12.0a.
Traceback (most recent call last):
File "/home/gloobal/PycharmProjects/Developments/migration/openupgrade/odoo/service/server.py", line 1118, in preload_registries
registry = Registry.new(dbname, update_module=update_module)
File "/home/gloobal/PycharmProjects/Developments/migration/openupgrade/odoo/modules/registry.py", line 86, in new
odoo.modules.load_modules(registry._db, force_demo, status, update_module)
File "/home/gloobal/PycharmProjects/Developments/migration/openupgrade/odoo/modules/loading.py", line 476, in load_modules
force, status, report, loaded_modules, update_module, models_to_check, upg_registry)
File "/home/gloobal/PycharmProjects/Developments/migration/openupgrade/odoo/modules/loading.py", line 360, in load_marked_modules
upg_registry=upg_registry,
File "/home/gloobal/PycharmProjects/Developments/migration/openupgrade/odoo/modules/loading.py", line 194, in load_module_graph
migrations.migrate_module(package, 'pre')
File "/home/gloobal/PycharmProjects/Developments/migration/openupgrade/odoo/modules/migration.py", line 199, in migrate_module
migrate(self.cr, installed_version)
File "/usr/local/lib/python3.6/dist-packages/openupgradelib-3.0.0-py3.6.egg/openupgradelib/openupgrade.py", line 1691, in wrapped_function
if use_env2 else cr, version)
File "/home/gloobal/PycharmProjects/Developments/gloobal-addons/oca_modules/sale-reporting/sale_layout_category_hide_detail/migrations/12.0.1.0.0/pre-migration.py", line 17, in migrate
""",
File "/usr/local/lib/python3.6/dist-packages/openupgradelib-3.0.0-py3.6.egg/openupgradelib/openupgrade.py", line 1158, in logged_query
cr.execute(query, args)
File "/home/gloobal/PycharmProjects/Developments/migration/openupgrade/odoo/sql_db.py", line 148, in wrapper
return f(self, *args, **kwargs)
File "/home/gloobal/PycharmProjects/Developments/migration/openupgrade/odoo/sql_db.py", line 225, in execute
res = self._obj.execute(query, params)
psycopg2.ProgrammingError: column "show_details" of relation "sale_order_line" does not exist

Worth mentioning this module was installed in previous version...this error tells me that new fields are not created when this sql update is running...any ideas?..thanks in advance.

@pedrobaeza
Copy link
Member

Indeed, it should be executed post update:

6430d92

AaronHForgeFlow pushed a commit to ForgeFlow/sale-reporting that referenced this issue Jan 3, 2020
AaronHForgeFlow pushed a commit to ForgeFlow/sale-reporting that referenced this issue Jan 3, 2020
AaronHForgeFlow pushed a commit to ForgeFlow/sale-reporting that referenced this issue Jan 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants