← Back to team overview

openerp-india team mailing list archive

[Bug 932827] Re: Upgrade from OpenERP6.1rc1 to nightly build 20120213 make database unusable

 

Hello,

By changing from RC1 to the 20120213 nightly build you are doing the equivalent of a minor release update, just as if you were upgrading from RC1 to RC2. As a result, you should start the server in upgrade mode for each database, i.e:
    ./openerp-server -d <MY_DB> -u all

This is a standard procedure for minor migration updates, in order to
synchronize the database structures and view definitions with the latest
developments.

In addition, it is recommended to test non-stable versions of OpenERP
with a new database every time, to avoid unnecessary upgrade steps
(after all, you're not supposed to use these test versions in production
anywhere).

BTW, upgrading from a stable version of OpenERP to the next major stable
version (e.g. 6.0 to 6.1) is not supported via the built-in upgrade
mechanism (-u all), since there may be more complex schema changes.

This is all explained in our release policy: http://bit.ly/openerp-
release-policy

Thanks,

** Changed in: openobject-addons
       Status: New => Invalid

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/932827

Title:
  Upgrade from OpenERP6.1rc1 to nightly build 20120213 make database
  unusable

Status in OpenERP Addons (modules):
  Invalid

Bug description:
  I had several databases with basic install and only demo data in
  OpenERP 6.1rc1 and upgraded using the nightly build deb package from
  http://nightly.openerp.com/6.1/deb/ first using Nightly build of
  January 27, then January 28, and last February 13th.

  After upgrading to the build of February 13th, none of the demo
  databases could login resulting in error screens with the following
  message:

  OpenERP Server Error
  Client Traceback (most recent call last):
    File "/usr/lib/pymodules/python2.6/openerp/addons/web/common/http.py", line 180, in dispatch
      response["result"] = method(controller, self, **self.params)
    File "/usr/lib/pymodules/python2.6/openerp/addons/web/controllers/main.py", line 464, in authenticate
      req.session.authenticate(db, login, password, env)
    File "/usr/lib/pymodules/python2.6/openerp/addons/web/common/session.py", line 73, in authenticate
      uid = self.proxy('common').authenticate(db, login, password, env)
    File "/usr/lib/pymodules/python2.6/openerp/addons/web/common/openerplib/main.py", line 117, in proxy
      result = self.connector.send(self.service_name, method, *args)
    File "/usr/lib/pymodules/python2.6/openerp/addons/web/common/http.py", line 611, in send
      raise fault

  
  Server Traceback (most recent call last):
    File "/usr/lib/pymodules/python2.6/openerp/addons/web/common/http.py", line 592, in send
      result = openerp.netsvc.dispatch_rpc(service_name, method, args)
    File "/usr/lib/pymodules/python2.6/openerp/netsvc.py", line 360, in dispatch_rpc
      result = ExportService.getService(service_name).dispatch(method, params)
    File "/usr/lib/pymodules/python2.6/openerp/service/web_services.py", line 384, in dispatch
      return fn(*params)
    File "/usr/lib/pymodules/python2.6/openerp/service/web_services.py", line 395, in exp_authenticate
      res_users = pooler.get_pool(db).get('res.users')
    File "/usr/lib/pymodules/python2.6/openerp/pooler.py", line 50, in get_pool
      return get_db_and_pool(db_name, force_demo, status, update_module)[1]
    File "/usr/lib/pymodules/python2.6/openerp/pooler.py", line 33, in get_db_and_pool
      registry = RegistryManager.get(db_name, force_demo, status, update_module, pooljobs)
    File "/usr/lib/pymodules/python2.6/openerp/modules/registry.py", line 138, in get
      update_module, pooljobs)
    File "/usr/lib/pymodules/python2.6/openerp/modules/registry.py", line 160, in new
      openerp.modules.load_modules(registry.db, force_demo, status, update_module)
    File "/usr/lib/pymodules/python2.6/openerp/modules/loading.py", line 298, in load_modules
      loaded_modules, processed_modules = load_module_graph(cr, graph, status, perform_checks=(not update_module), report=report)
    File "/usr/lib/pymodules/python2.6/openerp/modules/loading.py", line 179, in load_module_graph
      modobj.check(cr, 1, [module_id])
    File "/usr/lib/pymodules/python2.6/openerp/addons/base/module/module.py", line 612, in check
      if not mod.description:
    File "/usr/lib/pymodules/python2.6/openerp/osv/orm.py", line 476, in __getattr__
      return self[name]
    File "/usr/lib/pymodules/python2.6/openerp/osv/orm.py", line 391, in __getitem__
      field_values = self._table.read(self._cr, self._uid, ids, field_names, context=self._context, load="_classic_write")
    File "/usr/lib/pymodules/python2.6/openerp/osv/orm.py", line 3376, in read
      result = self._read_flat(cr, user, select, fields, context, load)
    File "/usr/lib/pymodules/python2.6/openerp/osv/orm.py", line 3435, in _read_flat
      cr.execute(query, (tuple(sub_ids),))
    File "/usr/lib/pymodules/python2.6/openerp/sql_db.py", line 152, in wrapper
      return f(self, *args, **kwargs)
    File "/usr/lib/pymodules/python2.6/openerp/sql_db.py", line 212, in execute
      res = self._obj.execute(query, params)
  ProgrammingError: column ir_module_module.auto_install does not exist
  LINE 1: ...e."complexity",ir_module_module."views_by_module",ir_module_...

  +++++

  Though not tested, I assume it would have worked if I had taken a
  backup of the data, and restored it, however, I believe a upgrade
  problem like this calls for an RC2 before final release since the
  differences are this big. Testing should also be made to make sure
  upgrades from 6.0.3 go smoothly with instructions for how an upgrade
  must be done to make sure the system remain usable before final
  release of 6.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/932827/+subscriptions


References