Passa al contenuto
È necessario essere registrati per interagire con la community.
Tutti gli articoli Persone Badge
Etichette (Mostra tutto)
odoo accounting v14 pos v15
Sul forum
La domanda è stata contrassegnata
migrationopenupgrademigration.py
4 Risposte
8647 Visualizzazioni
Avatar
Deepa Venkatesh

I had successfully migrated from Odoo 8 to Odoo 9, however 2 things i noticed which was not happening. Guess probably I would have missed a cue.


In the module say product, in which post-migration.py script exists, I had added additional SQL execute statement, to my surprise it didn't get executed !! strange


Secondly, openupgrade server is not considering my custom addon path, even though I had clearly specified in the config file, and the same is been explicitly passed while running migrate.py.

Am I missing something.



Avatar
Abbandona
Avatar
Deepa Venkatesh
Autore Risposta migliore

Added the solution, if anyone is looking for it.

Openupgrade creates a copy of addon in the tmp folder to perform its migration.

Hence first paste the link of custom-addon directory into that tmp folder.(/var/tmp/openupgrade/9.0/)

and then include those custom-addon in the file 'migrate.py'.

migrate.py 

migrations = {
    '9.0': {
        'addons': {
            'addons': {
                'type': 'link',
                'url': os.path.join('server', 'addons'),
            },
            'custom_addons': {
                'type': 'link',
                'url': os.path.join('custom_addons'),
            },
},


Note: If Custom addons exists for former version i.e 8.0 in this case, then the above steps applies for that as well. 


Avatar
Abbandona
Avatar
Emanuel Cino
Risposta migliore

For the addons path, I had the same surprise. It seems the addons are only taken from the ~/.local/share/Odoo/addons/9.0 folder. Place your addons here and it should work.

Avatar
Abbandona
Deepa Venkatesh
Autore

Thank you, sure indeed I tried this, not a bad idea, however I found its better not to mix our custom modules while running migrate script, I mean once the base module migration is done, then if we just re-update the 'base' module, this will port all our custom module successfully..

Deepa Venkatesh
Autore

But if you really want to include our custom path, then all you need to do is, copy custom addon into the tmp folder along with the addon, (note, openupgrade creates a copy of addon in the tmp folder to perform its migration) and there also exists a copy of migrate.py, in that we can append the custom-addon-name... this will help include our custom modules....

Do this, if it is really needed, else no need...

Post correlati Risposte Visualizzazioni Attività
Asset Management migration V12.0 to new versions
migration openupgrade
Avatar
0
mag 23
1917
How to set up 2 OpenUpgrade Servers Risolto
migration openupgrade
Avatar
1
ago 19
4202
Error openupgrade hr module
migration openupgrade
Avatar
Avatar
1
mar 15
5192
DB Migration Risolto
migration openupgrade odoo10.0 migration.py migrations
Avatar
Avatar
Avatar
4
dic 22
5268
Database Migration error from Odoo 14 to 15(Community) using Openeupgrade.
migration openupgrade databasemigration
Avatar
Avatar
1
mag 25
1628