Openbravo Issue Tracking System - Openbravo Deployment Options |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0008002 | Openbravo Deployment Options | Appliance rPath | public | 2009-03-06 12:59 | 2009-08-31 16:23 |
|
Reporter | plujan | |
Assigned To | jpabloae | |
Priority | urgent | Severity | critical | Reproducibility | have not tried |
Status | closed | Resolution | no change required | |
Platform | | OS | 5 | OS Version | |
Product Version | 2.40MP3 | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
Support ticket | |
OBNetwork customer | No |
|
Summary | 0008002: When migrating from 2.40mp2 to 2.40mp3 I got success on update, but I still have a 2.40mp2 |
Description | I updated 2.40mp2 to 2.40mp3 using OBN Console. After the successful update, I went to the application and I still see everything as in 2.40mp2.
Also the AD_Syteminfo table shows 2.40mp2
The administration console says that I am on 2.40mp3 |
Steps To Reproduce | |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2009-03-06 12:59 | plujan | New Issue | |
2009-03-06 12:59 | plujan | Assigned To | => jpabloae |
2009-03-06 12:59 | plujan | OBNetwork customer | => No |
2009-03-06 13:13 | jpabloae | Status | new => acknowledged |
2009-03-06 13:20 | jpabloae | Status | acknowledged => scheduled |
2009-03-06 13:20 | jpabloae | fix_in_branch | => pi |
2009-03-06 13:20 | jpabloae | Note Added: 0014483 | |
2009-03-06 13:20 | jpabloae | Status | scheduled => feedback |
2009-03-06 16:32 | plujan | Status | feedback => closed |
2009-03-06 16:32 | plujan | Note Added: 0014486 | |
2009-03-06 16:32 | plujan | Resolution | open => no change required |
2012-07-19 13:11 | gorka_gil | Category | Appliance stack => Appliance rPath |