View Issue Details

IDProjectCategoryView StatusLast Update
0001791RackTablesdefaultpublic2017-10-09 10:52
Reportercraig.gleasonAssigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version0.20.14 
Target VersionFixed in Version 
Summary0001791: Upgrade to 0.20.14
DescriptionHello – Is there any documentation on how you perform an upgrade of Racktables on RHEL 6.4 – 0.20.10 is currently installed and would like to upgrade to 0.20.14. The information in the readme is a little sparse.
Steps To ReproduceTried following what is in the readme, but, when you open the URL, it starts off at step 3 – DB setup….which doesn’t seem correct. No upgrade message is shown.
TagsNo tags attached.

Activities

infrastation

infrastation

2017-09-27 10:38

administrator   ~0003715

What is the message above the URL that you open?
craig.gleason

craig.gleason

2017-09-27 21:01

reporter   ~0003717

when I entered http://<node>/racktables it redirected me to racktables/wwwroot/?module=installer
infrastation

infrastation

2017-09-27 22:09

administrator   ~0003719

There are a few strange things about this issue.

1. When RackTables prompts to install or to upgrade, it does not redirect. It returns a page with a message and a link and it is up to the user whether to follow the link.
2. When RackTables URI is "/racktables/", it will never redirect a user to "/racktables/wwwroot/".
3. The installer always starts at step 1.
4. After the upgrade RackTables never prompts to run the installer (unless the upgrade involved removing secret.php).

It would help if you double-checked everything and provided exact steps to reproduce the problem.
craig.gleason

craig.gleason

2017-09-27 23:03

reporter   ~0003721

As the upgrade instruction consisted of:
# How to upgrade RackTables

0. **Backup your database** and check the release notes below before actually
   starting the upgrade.
1. Remove all existing files except configuration (the `inc/secret.php` file)
   and local plugins (in the `plugins/` directory).
2. Put the contents of the new tar.gz/zip archive into the place.
3. Open the RackTables page in a browser. The software will detect version
   mismatch and display a message telling to log in as admin to finish
   the upgrade.
4. Do that and report any errors to the bug tracker or the mailing list.


The easiest way to remove all the existing files was just rename the racktable directory, create a new one, restore the inc/secret.php file and the plugins directory. Then, place the contents of the new release into the racktables directory.
infrastation

infrastation

2017-10-05 19:03

administrator   ~0003729

One actual bug I can confirm is that in RackTables 0.20.14 at installer step 4 if the code fails to require secret.php (after the user has likely adjusted the permissions as advised on the previous page) it ends ups in a blank page and an error in the log file:

PHP Fatal error: require_once(): Failed opening required '/usr/local/racktables/wwwroot/inc/secret.php' (include_path='.:/usr/share/php') in /usr/local/racktables/wwwroot/inc/pre-init.php on line 48

But in the first place the installer does not start when secret.php is present.
craig.gleason

craig.gleason

2017-10-06 00:12

reporter   ~0003731

Looking in the web server log, I do see the PHP Fatal error that you mentioned - any idea how to resolve it? Maybe try 0.21.0?
infrastation

infrastation

2017-10-06 16:15

administrator   ~0003733

To resolve the failure to require secret.php it would help to make the file readable (as much as the web-server process is concerned, specifically). To understand other issues mentioned here it would help to read my comment 4 comments before and provide the specific information it requests.
craig.gleason

craig.gleason

2017-10-06 18:44

reporter   ~0003735

What information are you asking for? I provided the steps taken for the upgrade.
craig.gleason

craig.gleason

2017-10-09 10:52

reporter   ~0003737

changing the protection to 755 on secret.php resulted in the login being displayed - in version 0.20.10 I did not have to do this....in any case, the problem is resolved.

Issue History

Date Modified Username Field Change
2017-09-27 03:16 craig.gleason New Issue
2017-09-27 10:38 infrastation Note Added: 0003715
2017-09-27 21:01 craig.gleason Note Added: 0003717
2017-09-27 22:09 infrastation Note Added: 0003719
2017-09-27 23:03 craig.gleason Note Added: 0003721
2017-10-01 15:05 infrastation Status new => feedback
2017-10-05 19:03 infrastation Note Added: 0003729
2017-10-06 00:12 craig.gleason Note Added: 0003731
2017-10-06 00:12 craig.gleason Status feedback => new
2017-10-06 16:15 infrastation Note Added: 0003733
2017-10-06 18:44 craig.gleason Note Added: 0003735
2017-10-09 10:52 craig.gleason Note Added: 0003737