[MCOL-875] 1.1.0 upgrade install issue Created: 2017-08-14 Updated: 2017-09-13 Resolved: 2017-09-13 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | installation |
| Affects Version/s: | 1.1.0 |
| Fix Version/s: | 1.1.0 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | David Hill (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
amazon binary root install |
||
| Sprint: | 2017-16, 2017-17, 2017-18 |
| Description |
|
Doing an upgrade install from 1.0.11 to 1.1.0, I get this error when running postConfigure [root@ip-172-30-0-161 bin]# ./postConfigure -u -p Calpont1 The error doesn't happen when I do a fresh install... |
| Comments |
| Comment by David Hall (Inactive) [ 2017-08-14 ] |
|
This happens because we changed the version number of libudfsdk - the library changed names from libudfsdk.so.1.0.0 to libudfsdk.so.1.1.0. During the upgrade, the old library is left and the new library added. The symlink libudfsdk.so.1 continues to point to libudfsdk.so.1.0.0. If you remove the old lib before the upgrade, then the symlink gets set correctly. |
| Comment by David Hill (Inactive) [ 2017-08-14 ] |
|
Ok, I will need to add that to the upgrade Document... OR we need to add to 1.1.0 post-install script to remove. Which is probably what needs to happen because multi-node installs will be a pain to do manually |
| Comment by David Hill (Inactive) [ 2017-08-31 ] |
|
problem only exist on binary installs, rpm will do the correct cleanup |
| Comment by David Hill (Inactive) [ 2017-08-31 ] |
|
fixed with changes to post-install to move the older libudk files from 1.0.x |
| Comment by Daniel Lee (Inactive) [ 2017-09-13 ] |
|
Build verified: 1.1.0-1 Upgraded 1.0.11-1 to 1.1.0-1 |