[MCOL-3887] Postconfig problem processing an upgrade Created: 2020-03-16 Updated: 2020-11-12 Resolved: 2020-05-04 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 1.4.3 |
| Fix Version/s: | 1.4.4, 1.5.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Patrick LeBlanc (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2020-4, 2020-5, 2020-6, 2020-7 |
| Description |
|
Found a problem when running the upgrade code in postConfigure. It's been looking in the wrong place for the columnstore.cnf.rpmsave file, so the mycnfUpgrade program must have been exiting with an error code since Sept. |
| Comments |
| Comment by Patrick LeBlanc (Inactive) [ 2020-03-16 ] |
|
The PR for 1.5: https://github.com/mariadb-corporation/mariadb-columnstore-engine/pull/1107 |
| Comment by Daniel Lee (Inactive) [ 2020-05-04 ] |
|
Build verified: 1.4.4-1, 1.5.0-1 source 1.4.4-1 /root/ColumnStore/buildColumnstoreFromGithubSource/server /root/ColumnStore/buildColumnstoreFromGithubSource/server/engine 1.5.0-1 /root/ColumnStore/buildColumnstoreFromGithubSource/server commit 6ad38ccc28d31a099d052e5de827543808843a3c Reproduced this issue in 1.4.3.1: r1pm1: Do you want to utilize the configuration data from the saved copy? [y,n] > y and verified the fix in 1.4.4-1 and 1.5.0-1 |