Generate Records Issue in 6.0 openupgrade-server

Bug #1009344 reported by muralikrishnareddy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenUpgrade Server
Triaged
Undecided
Stefan Rijnhart (Opener)

Bug Description

In OPenupgrade-server/6.0 , i installed the Openupgrade development module, after installing some modules/install All modules
 when i click on Generate Records, its showing an error as below :

Environment Information :
System : Linux-2.6.32-21-generic-i686-with-Ubuntu-10.04-lucid
OS Name : posix
Distributor ID: Ubuntu
Description: Ubuntu 10.04 LTS
Release: 10.04
Codename: lucid
Operating System Release : 2.6.32-21-generic
Operating System Version : #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010
Operating System Architecture : 32bit
Operating System Locale : en_IN.ISO8859-1
Python Version : 2.6.5
OpenERP-Client Version : 6.0.3
Last revision No. & ID :1938 <email address hidden>
Traceback (most recent call last):
  File "/home1/muraliv/upgrade_6.0_new/6.0/bin/netsvc.py", line 489, in dispatch
    result = ExportService.getService(service_name).dispatch(method, auth, params)
  File "/home1/muraliv/upgrade_6.0_new/6.0/bin/service/web_services.py", line 599, in dispatch
    res = fn(db, uid, *params)
  File "/home1/muraliv/upgrade_6.0_new/6.0/bin/osv/osv.py", line 122, in wrapper
    return f(self, dbname, *args, **kwargs)
  File "/home1/muraliv/upgrade_6.0_new/6.0/bin/osv/osv.py", line 176, in execute
    res = self.execute_cr(cr, uid, obj, method, *args, **kw)
  File "/home1/muraliv/upgrade_6.0_new/6.0/bin/osv/osv.py", line 167, in execute_cr
    return getattr(object, method)(cr, uid, *args, **kw)
  File "/home1/muraliv/upgrade_6.0_new/6.0/bin/addons/openupgrade_records/model/generate_records_wizard.py", line 85, in generate
    self.write(cr, uid, ids, {'state': 'ready'})
  File "/home1/muraliv/upgrade_6.0_new/6.0/bin/osv/orm.py", line 2003, in write
    self.datas[object_id].update(vals2)
KeyError: 1

Thanks,
Murali Krishna,

Revision history for this message
Stefan Rijnhart (Opener) (stefan-opener) wrote :

Hi Murali,

looks like the osv_memory resource that constitutes the wizard is being cleared up before the operation finishes. Can you verify that this does not happen when you set the 'osv_memory_age_limit' configuration option to a higher value (e.g. 5)?

Cheers,
Stefan.

Changed in openupgrade-server:
assignee: nobody → Stefan Rijnhart (Therp) (stefan-therp)
status: New → Triaged
Revision history for this message
muralikrishnareddy (muralikrishna-velamuru) wrote :

Hi Stefan,

In server/6.0/doc/openerp-server.conf file i added an option as :

osv_memory_age_limit = 5.0

Still, i am facing the same problem as above,

Thanks,
Murali

Revision history for this message
muralikrishnareddy (muralikrishna-velamuru) wrote :

HI Stefan,

First time when i click on Generate Records,

...
[2012-06-06 16:32:42,107][v6_hr_new_1] INFO:init:module hr: loading hr_data.xml
[2012-06-06 16:32:42,225][v6_hr_new_1] INFO:init:module hr: loading board_hr_view.xml
[2012-06-06 16:32:42,392][v6_hr_new_1] INFO:init:module hr: loading board_hr_manager_view.xml
[2012-06-06 16:32:42,460][v6_hr_new_1] INFO:init:module hr: loading hr_demo.xml
[2012-06-06 16:32:42,879][v6_hr_new_1] INFO:init:module hr: loading hr_department_demo.xml
[2012-06-06 16:32:43,303][v6_hr_new_1] INFO:init:module hr: loading test/test_hr.yml
[2012-06-06 16:32:43,743][v6_hr_new_1] WARNING:init:object openupgrade.comparison.config (openupgrade.comparison.config) has no access rules!
[2012-06-06 16:32:44,019][v6_hr_new_1] INFO:init:[01]: Assertions report:
[2012-06-06 16:32:44,019][v6_hr_new_1] INFO:init:[02]: Level success failed
[2012-06-06 16:32:44,019][v6_hr_new_1] INFO:init:[03]: error 1 0
[2012-06-06 16:32:44,020][v6_hr_new_1] INFO:init:[04]: total 1 0
[2012-06-06 16:32:44,020][v6_hr_new_1] INFO:init:[05]: end of report (1 assertion(s) checked)

Like this its showing at server and Continue Button in Generate Records get Enabled,
When i Click Continue button again that time the above error is coming.

Thanks,
Murali,

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.