[MCOL-928] postConfigure is not detecting glusterfs on Debian9.1 for non-root user Created: 2017-09-18  Updated: 2017-10-30  Resolved: 2017-10-30

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 1.1.0
Fix Version/s: 1.1.1

Type: Bug Priority: Critical
Reporter: Daniel Lee (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2017-19, 2017-20, 2017-21, 2017-22

 Description   

Build tested: 1.1.0 beta

postConfigure is not detecting glusterfs on Debian9.1 for non-root user. As a result, DataRedundancy storage type is not available.

 Comments   
Comment by Ben Thompson (Inactive) [ 2017-10-26 ]

postConfigure should detect gluster installs on Debian9.1

Comment by David Hill (Inactive) [ 2017-10-26 ]

reviewed by David Hill

Comment by Daniel Lee (Inactive) [ 2017-10-30 ]

Build verified: 1.1.1.-1 Debian 9.1 deb package.

Installed a 1um4pm gluster stack. DataRedundancy storage type was available

==> s2pm1: There are 3 options when configuring the storage: internal, external, or DataRedundancy
==> s2pm1:
==> s2pm1: 'internal' - This is specified when a local disk is used for the DBRoot storage.
==> s2pm1: High Availability Server Failover is not Supported in this mode
==> s2pm1:
==> s2pm1: 'external' - This is specified when the DBRoot directories are mounted.
==> s2pm1: High Availability Server Failover is Supported in this mode.
==> s2pm1:
==> s2pm1: 'DataRedundancy' - This is specified when gluster is installed and you want
==> s2pm1: the DBRoot directories to be controlled by ColumnStore Data Redundancy.
==> s2pm1: High Availability Server Failover is Supported in this mode.
==> s2pm1: NOTE: glusterd service must be running and enabled on all PMs.
=> s2pm1: Select the type of Data Storage [1=internal, 2=external, 3=DataRedundancy] (1) >
==> s2pm1: 3
==> s2pm1:

Generated at Thu Feb 08 02:24:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.