Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0010938 | Openbravo ERP | A. Platform | public | 2009-10-13 10:33 | 2010-03-22 10:52 |
|
| Reporter | networkb | |
| Assigned To | iciordia | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | acknowledged | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | 2.50MP6 | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0010938: There is not a way to rollback an update when updating the core of the application |
| Description | There is not a way to rollback an update when updating the core of the application. If you get errors during the updating of an application,
if you get errors, there is no way to rollback the application to the previous release. |
| Steps To Reproduce | -Access to an application
-update to a new mp using a obx file.
-Try to rollback to the previous maintenance pack |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | feature request | 0009059 | | new | iciordia | Have the ability to roll back a core update if the build process goes wrong |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-10-13 10:33 | networkb | New Issue | |
| 2009-10-13 10:33 | networkb | Assigned To | => rafaroda |
| 2009-10-15 16:37 | psarobe | Note Added: 0021068 | |
| 2009-10-15 16:37 | psarobe | Assigned To | rafaroda => iciordia |
| 2009-10-15 16:37 | psarobe | Status | new => acknowledged |
| 2009-10-16 12:03 | psarobe | Relationship added | related to 0009059 |
| 2009-10-19 12:55 | iciordia | Note Added: 0021174 | |
| 2009-10-19 12:55 | iciordia | Priority | immediate => normal |
| 2009-10-19 12:55 | iciordia | Type | defect => feature request |
| 2009-10-19 12:55 | iciordia | Target Version | 2.50MP8 => |
| 2010-03-22 09:58 | networkb | Note Added: 0025636 | |
| 2010-03-22 10:52 | iciordia | Note Added: 0025639 | |
|
Notes |
|
|
|
|
Waiting for Isma's feedback |
|
|
|
|
This is not a bug but a feature request
It is possible to do backup before installing and recovery if it fails
Openbravo prof. subscription (rpath instances) can do it through the console
This fr will not be done in short term, in order to properly do this we need add a different context -ob manager- to take care about module installation, backups, recovery, etc. (you can not recover from the context you are recovering)
Ismael |
|
|
|
|
|
Shen the backup of the core and modules is done before update, a backup of the database should be done in order to be able to recover all the system |
|
|
|
|
Not sure if I understand the previous note, but we decided not to do a full backup during the install process because of several reasons:
-recovery can not be started from this process as explained above in this thread
-it should be in sync with the backup mechanism in the system (eg. provided by openbravo appliance)
-performance issues (update process much slower, incremental backups would be better)
My previous note is still valid: we done plan to address this problem in the short term, and Openbravo customers can easily work-around this issue.
Ismael |
|