Fatal error when trying to run CLI upgrade script after clean install of 15.04dev
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Aaron Wells | ||
1.10 |
Fix Released
|
High
|
Aaron Wells | ||
15.04 |
Fix Released
|
High
|
Aaron Wells |
Bug Description
To replicate:
1. Do a clean install of Mahara (using either the CLI installer or the web installer.)
2. After install is done, run the upgrade script (either CLI, or by going to /admin/upgrade.php
Expected Results: Since there's nothing to upgrade, it should finish with no problems.
Actual result:
[INF] 7c (admin/
[INF] 7c (lib/mahara.
[INF] 7c (lib/upgrade.
[DBG] 7c (lib/mahara.
[DBG] 7c (lib/mahara.
[DBG] 7c (lib/mahara.
[DBG] 7c (lib/dml.php:147) postgres7 error: [-18: ERROR: relation "artefact_
[DBG] 7c (lib/dml.php:147) Command was: ALTER TABLE "artefact_
[WAR] 7c (lib/errors.
Call stack (most recent first):
* log_message("Could not execute command: ALTER TABLE "artefact_b...", 8, true, true) at /home/aaronw/
* log_warn("Could not execute command: ALTER TABLE "artefact_b...") at /home/aaronw/
* SQLException-
* execute_sql("ALTER TABLE {artefact_
* xmldb_core_
* upgrade_
* upgrade_
[WAR] 7c (lib/dml.php:148) Could not execute command: ALTER TABLE "artefact_
Call stack (most recent first):
* execute_sql("ALTER TABLE {artefact_
* xmldb_core_
* upgrade_
* upgrade_
Changed in mahara: | |
status: | Fix Committed → Fix Released |
Used git bisect to identify this commit as the source of the problem:
commit 847754aaacade14 30aac99c40c6378 b642cf3c1b
Author: Aaron Wells <email address hidden>
Date: Thu Oct 23 12:48:17 2014 +1300
Add a <meta name="generator"> tag with the Mahara major version number
Bug 1384497. This also adds a new $config->series to lib/version.php,
which stores the major version (or as we sometimes call it, "the series")
of the current release. It seemed better to store this separately rather
than to try to parse it from $config->release, because we may change
our release numbering strategy in the future.
Change-Id: If4c0d7352e9433 cdaf54a03bb9223 56d6c950e7d
The problem is also present in 1.10_STABLE from this commit being backported there. The problem is not present in 1.8_STABLE or 1.9_STABLE, however. Perhaps it was fixed by this commit (present in 1.8_STABLE & 1.9_STABLE but not 1.10_STABLE):
Fixing a backporting mistake (Bug #1384497)
Older versions handle the check_upgrades() output
differently
Change-Id: I7b847d814a504e a4a15f1c7b8a1a9 e5d008299bf
Signed-off-by: Robert Lyon <email address hidden>