Project

General

Profile

Bug #5880

re-enabling upgrade in RPM startup script

Added by Marco Mambelli over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Urgent
Category:
-
Target version:
Start date:
04/11/2014
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

In 5071 I disabled the upgrade command for the RPM startup scripts.
The files are over-written by the RPM upgrade but in the instructions we ask to run 'upgrade' and not 'reconfig'.
Pending investigation on why that is necessary I'm re-enabling it for 3.2.4
Marco

History

#1 Updated by Marco Mambelli over 5 years ago

I did a branch v3/5880 and committed the changes.
I commented the code doing the check for RPM version and giving an error (when upgrade request is issued)
I commented instead of removing the lines because I want to go back to it for 3.2.5. There should be non need for upgrade in the RPM version

fixed 2 more problems with the startup script noticed in the ROM testing.
1. It was never setting the condition for RPM installation. This was effecting only the checks on what is valid because the directories and config files were set to the correct value and there are no other differences in behavior.
2. the upgrade function in the factory was not parsing correctly the parameters

#2 Updated by Parag Mhashilkar over 5 years ago

Closing the issues that were take care of in v3.2.4

#3 Updated by Parag Mhashilkar over 5 years ago

  • Status changed from New to Closed


Also available in: Atom PDF