c2c-oerpscenario team mailing list archive

[xrg <xrg@xxxxxxxxx>]

On Friday 08 April 2011, you wrote:
> Hmm
> what about rolling back the transaction (the complete install/update)?

It does roll back.
But the process of _selecting_ packages for installation belongs to an earlier 
transaction. So, you mark the packages, and next time you try to start the 
servers, the actual installation transaction may happen. The reason is that 
these are different wizard steps, and cannot thus be in a single transaction. 
Ah, yes, also, when upgrading packages, the pooler does restart, so we need to 
have a persistent state in postgres.

As a corrective step, you should _unselect_ the marked packages after your 
"apply selected install/updates" has failed and before any restart of the 
server. I appreciate that many admins will forget to do that, and therefore 
end up in the situation you describe.



-- 
Say NO to spam and viruses. Stop using Microsoft Windows!

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/754373

Title:
  install + update: error in xml prohibts serverrestart

Status in OpenERP Server:
  New

Bug description:
  if for some reasons (coding or reference error) loading of xml fails
  the module remains in state "to be installed/updated" and the server
  does not restart any more

  IMHO a better and more userfriendly solution would be to set all modules to be installed/updated to a safe state "uninstalled" if a xml loading error occurs
  or to allow the server to reastart without loading