[MCOL-3498] S3 Invalid entry inserted into ~/.bashrc when non-distributed installation is used Created: 2019-09-10 Updated: 2019-10-11 Resolved: 2019-10-11 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | installation |
| Affects Version/s: | 1.4.0 |
| Fix Version/s: | 1.4.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Build tested: 1.4.0-1 server commit: This issue occurs only when S3 (both localStorage or S3) storage option (option #4) is selected on a non-distributed installation over multiple nodes. I tested on a 1um2pm stack. The ~/.bashrc file on non-pm1 nodes (um1 and pm2 in my test stack) has the following entry at the end of the file. . /usr/local/mariadb/columnstore/bin/ This entry is invalid and it cause the following error when the user logs in: root@127.0.0.1's password: While postConfigure is being executed, I monitored PM2's .bashrc file. The entry seemed to have been inserted from the point where postConfigure tries to start up the stack. |
| Comments |
| Comment by Ben Thompson (Inactive) [ 2019-10-03 ] |
|
I don't believe this is related to S3 storage at all, I think i've seen this with internal storage as well. |
| Comment by Ben Thompson (Inactive) [ 2019-10-03 ] |
|
This shows up based on some changes to remove HDFS storage options. Need to clean out more of this code. |
| Comment by Daniel Lee (Inactive) [ 2019-10-11 ] |
|
Builds verified: 1.4.0-1 beta and 1.4.1-1 Verified both with and without S3. 1.4.0-1 beta 1.4.1-1 [dlee@master centos7]$ cat gitversionInfo.txt The issue was identity during development. It has been correct since. |