name 'get_phantom_bom_id' is not defined

Bug #809168 reported by Aline (OpenERP)
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Fix Released
High
OpenERP's Framework R&D

Bug Description

tested in web and trunk

to reproduce :
 - create a db
 - install sales warehouse and mrp

bug

[2011-07-12 09:18:49,638][test_webr_120711] INFO:init:module sale: loading sale_demo.xml
[2011-07-12 09:18:51,005][test_webr_120711] ERROR:tools.convert.xml_import:Parse error in /home/aline/openerp/addons/trunk/sale/sale_demo.xml:182:
<function model="procurement.order" name="run_scheduler"/>
Traceback (most recent call last):
  File "/home/aline/openerp/server/trunk/openerp/tools/convert.py", line 888, in parse
    self._tags[rec.tag](self.cr, rec, n)
  File "/home/aline/openerp/server/trunk/openerp/tools/convert.py", line 366, in _tag_function
    _eval_xml(self,rec, self.pool, cr, uid, self.idref, context=context)
  File "/home/aline/openerp/server/trunk/openerp/tools/convert.py", line 192, in _eval_xml
    res = getattr(model, method)(cr, uid, *args)
  File "/home/aline/openerp/addons/trunk/procurement/procurement.py", line 473, in run_scheduler
    self._procure_confirm(cr, uid, use_new_cursor=use_new_cursor, context=context)
  File "/home/aline/openerp/addons/trunk/procurement/schedulers.py", line 74, in _procure_confirm
    wf_service.trg_validate(uid, 'procurement.order', proc.id, 'button_check', cr)
  File "/home/aline/openerp/server/trunk/openerp/workflow/wkf_service.py", line 80, in trg_validate
    res2 = instance.validate(cr, id, ident, signal)
  File "/home/aline/openerp/server/trunk/openerp/workflow/instance.py", line 48, in validate
    workitem.process(cr, witem, ident, signal, force_running, stack=stack)
  File "/home/aline/openerp/server/trunk/openerp/workflow/workitem.py", line 61, in process
    ok = _split_test(cr, workitem, activity['split_mode'], ident, signal, stack)
  File "/home/aline/openerp/server/trunk/openerp/workflow/workitem.py", line 156, in _split_test
    if wkf_expr.check(cr, workitem, ident, transition,signal):
  File "/home/aline/openerp/server/trunk/openerp/workflow/wkf_expr.py", line 81, in check
    return _eval_expr(cr, ident, workitem, transition['condition'])
  File "/home/aline/openerp/server/trunk/openerp/workflow/wkf_expr.py", line 58, in _eval_expr
    ret = eval(line, env, nocopy=True)
  File "/home/aline/openerp/server/trunk/openerp/tools/safe_eval.py", line 285, in safe_eval
    return eval(test_expr(expr,_SAFE_OPCODES, mode=mode), globals_dict, locals_dict)
  File "", line 1, in <module>
NameError: name 'get_phantom_bom_id' is not defined

Related branches

Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

Seems to be caused by a change yesterday in the module loading system.. under investigation. Happens if you install MRP and then later Sales, for example.

affects: openobject-client-web → openobject-server
Changed in openobject-server:
importance: Undecided → High
status: New → In Progress
Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

Server-side change was: revno: 3502 [merge] revision-id: <email address hidden>

Changed in openobject-server:
assignee: nobody → OpenERP's Framework R&D (openerp-dev-framework)
Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

Fix landed in server at revision 3505 revid <email address hidden>.

After the recent change to make module install atomically (code *and* data), we ran into issues when installing a new module indirectly triggers code of a not-yet-loaded-but-installed module, via its data that is already in the database (e.g. worflows or reports modified by this module within another module, that now refer to its code). To avoid this, we now make sure that we only install new modules on top of a consistent system (code *and* data), by loading all installed or 'to upgrade' modules *before* starting to install new ones.

Changed in openobject-server:
milestone: none → 6.1
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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