Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
5.6.3, 6.1.1
-
2021-16, 2021-17
Description
Multiple user experience issues popping up
Steps to reproduce attached and a video
- When upgrading/installing from CS 5 to 6, columnstore and mysql customizations are lost - worse, you cant even startup columnstore until you swap back in the old customization
- Logs under /var/log/mariadb/columnstore/* have weird permissions, some root:root others mysql:mysql
- I couldn't test installing cmapi 1.4 or 1.5 where the name was different to test upgrade impact as the lastest cs 5.6.3 now comes with cmapi 1.6 but clients running the older versions have the older cmapi.
Expected:
After installing CS 6, at least my columnstore configurations would be put back into place so that I can turn on columnstore.
Actual:
During the uninstall of CS 5, Columnstore.xml gets moved to Columnstore.xml.rpmsave and never moved back automatically. causing customer experience issues as cmapi loses its API key configuration, the columnstore.xml doesn't know its part of a cluster, and cmapi 1.6 blocks using systemctl start mariadb-columnstore (for the better else i'd be worse).
Attachments
Issue Links
- relates to
-
MCOL-4979 Upgrade Experience | CMAPI doesnt load old cmapi_server.conf after uninstall
- Closed