Openbravo Issue Tracking System - Openbravo ERP | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0007562 | Openbravo ERP | A. Platform | public | 2009-02-13 17:37 | 2009-04-22 00:00 |
Reporter | mtaal | ||||
Assigned To | marvintm | ||||
Priority | high | Severity | major | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Platform | OS | 5 | OS Version | ||
Product Version | pi | ||||
Target Version | pi | Fixed in Version | 2.50beta | ||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | No | ||||
Web browser | |||||
Modules | Core | ||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0007562: Update of module status fails resulting in difficult to understand issues later in the build process | ||||
Description | The status of modules is updated in the beginning of the buildprocess: in the database.postupdate step. If this fails (see below [1]) then this results in the following unpredictable behavior: - the status of the core module is not set to P - in the apply module step later in the build the referencedata of the module is not imported (this is the referencedata/standard/Masterdata.xml) because the core module does not have the correct status - the import of sample data fails because it misses data, the error message of the import.sample.data is: [importsampledata] org.openbravo.base.exception.OBException: org.hibernate.PropertyValueException: not-null property references a null or transient value: Currency.iSOCode [1] [sql] Failed to execute: UPDATE AD_MODULE SET ISINDEVELOPMENT='N', ISDEFAULT='N', SEQNO=NULL, STATUS='P', UPDATE_AVAILABLE=NULL, ISREGISTERED='N' WHERE STATUS IS NULL OR STATUS='I' [sql] org.postgresql.util.PSQLException: ERROR: The version has to be formatted like x.y.z where x, y and z are integers. [sql] 9 of 10 SQL statements executed successfully | ||||
Steps To Reproduce | |||||
Proposed Solution | Proposed solution: - perform the update statement for each module separately - let the build fail if the update statements do not finish correctly | ||||
Additional Information | |||||
Tags | Modularity | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2009-02-13 17:37 | mtaal | New Issue | |||
2009-02-13 17:37 | mtaal | Assigned To | => rafaroda | ||
2009-02-13 17:37 | mtaal | OBNetwork customer | => No | ||
2009-02-13 17:37 | mtaal | Regression testing | => No | ||
2009-02-13 17:39 | mtaal | Assigned To | rafaroda => marvintm | ||
2009-02-17 18:23 | rafaroda | Priority | normal => high | ||
2009-02-17 18:23 | rafaroda | Status | new => scheduled | ||
2009-02-17 18:33 | rafaroda | Tag Attached: Modularity | |||
2009-02-18 12:45 | svnbot | Checkin | |||
2009-02-18 12:45 | svnbot | Note Added: 0013637 | |||
2009-02-18 12:45 | svnbot | Status | scheduled => resolved | ||
2009-02-18 12:45 | svnbot | Resolution | open => fixed | ||
2009-02-18 12:45 | svnbot | svn_revision | => 13307 | ||
2009-04-21 10:33 | psarobe | Status | resolved => closed | ||
2009-04-22 00:00 | anonymous | sf_bug_id | 0 => 2777939 |
Notes | |||||
|
|||||
|
|