1.4.3 Columnstore Amazon install doesnt work when using existing EBS for dbroot

Reported by customer and reproduced. Customer trying to install 1.4.3 using the Amazon EC2 setup using the Amazon AWS CLI Tools option with EBS storage. This is something that has been support in older versions, like 1.1 and 1.2. Customer tried it in 1.4 and it didnt work. They created their own EBS storage to use for the DBRoot and it stop during postConfigure installation. I reproduced the same issue.

From customer:

Our Ansible script created the nodes and the volumes, but did not mount the volumes.
Running posrConfigure, seems to be stalled here:

----- Performance Module Configuration -----

Enter number of Performance Modules [1,1024] (1) > 2

• • • Parent OAM Module Performance Module #1 Configuration ***

EC2 Instance ID for pm1: i-0305ac7f2227f09fa
Getting Private IP Address for Instance i-0305ac7f2227f09fa, please wait...
Private IP Address of i-0305ac7f2227f09fa is 10.233.53.251

Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm1' (1) >

• • • Setup External EBS Volume for DBRoot #1 ***

• • • NOTE: You have the option to provide an
      existing EBS Volume ID or have a Volume created

Create a new EBS volume for DBRoot #1 ? [y,n] > n
Enter Volume ID for 'DBRoot1' () > vol-0bafb96c44f52b3f6

1. So this is where its is currently sitting.

----------------------------------------
In my testing using a single pm install

sudo /usr/bin/postConfigure

This is the MariaDB ColumnStore System Configuration and Installation tool.
It will Configure the MariaDB ColumnStore System and will perform a Package
Installation of all of the Servers within the System that is being configured.

IMPORTANT: This tool requires to run on the Performance Module #1

Prompting instructions:

Press 'enter' to accept a value in (), if available or
Enter one of the options within [], if available, or
Enter a new value

A copy of the MariaDB ColumnStore Configuration file has been saved during Package install.
It's Configured for a Multi-Server Install.
You have an option of utilizing the configuration data from that file or starting
with the MariaDB ColumnStore Configuration File that comes with the MariaDB ColumnStore Package.
You will only want to utilize the old configuration data when performing the same
type of install, i.e. Single or Multi-Server

Do you want to utilize the configuration data from the saved copy? [y,n] > n

===== Setup System Server Type Configuration =====

There are 2 options when configuring the System Server Type: single and multi

'single' - Single-Server install is used when there will only be 1 server configured
on the system. It can also be used for production systems, if the plan is
to stay single-server.

'multi' - Multi-Server install is used when you want to configure multiple servers now or
in the future. With Multi-Server install, you can still configure just 1 server
now and add on addition servers/modules in the future.

Select the type of System Server install [1=single, 2=multi] (2) > 2

===== Setup System Module Type Configuration =====

There are 2 options when configuring the System Module Type: separate and combined

'separate' - User and Performance functionality on separate servers.

'combined' - User and Performance functionality on the same server

Select the type of System Module Install [1=separate, 2=combined] (1) > 2

Combined Server Installation will be performed.
The Server will be configured as a Performance Module.
All MariaDB ColumnStore Processes will run on the Performance Modules.

NOTE: The MariaDB ColumnStore Schema Sync feature will replicate all of the
schemas and InnoDB tables across the User Module nodes. This feature can be enabled
or disabled, for example, if you wish to configure your own replication post installation.

MariaDB ColumnStore Schema Sync feature is Enabled, do you want to leave enabled? [y,n] >

NOTE: Amazon AWS CLI Tools are installed and allow MariaDB ColumnStore
to create Instances and EBS Volumes

Do you want to have ColumnStore use the Amazon AWS CLI Tools [y,n] >

NOTE: MariaDB ColumnStore Replication Feature is enabled

Enter System Name (columnstore-1) >

===== Setup Storage Configuration =====

----- Setup Performance Module DBRoot Data Storage Mount Configuration -----

Columnstore supports the following storage options...
1 - internal. This uses the linux VFS to access files and does
not manage the filesystem.
2 - external *. If you have other mountable filesystems you would
like ColumnStore to use & manage, select this option.
3 - GlusterFS * Note: glusterd service must be running and enabled on
all PMs.
4 - S3-compatible cloud storage *. Note: that should be configured
before running postConfigure (see storagemanager.cnf)

• - This option enables data replication and server failover in a
  multi-node configuration.

These options are available on this system: [1, 2, 4]
Select the type of data storage (1) > 2

NOTE: The volume type. This can be gp2 for General Purpose SSD, io1 for
Provisioned IOPS SSD, st1 for Throughput Optimized HDD, sc1 for Cold
HDD, or standard for Magnetic volumes.

Enter EBS Volume Type (gp2, io1, sc1, st1, standard) : (gp2) >

Enter EBS Volume storage size in GB: [1,16384] (1) >

===== Setup Memory Configuration =====

NOTE: Setting 'NumBlocksPct' to 50%
Setting 'TotalUmMemory' to 25%

===== Setup the Module Configuration =====

Amazon Install: For Module Configuration, you have the option to provide the
existing Instance IDs or have the Instances created.
You will be prompted during the Module Configuration setup section.

----- Performance Module Configuration -----

Enter number of Performance Modules [1,1024] (1) >

• • • Parent OAM Module Performance Module #1 Configuration ***

EC2 Instance ID for pm1: i-0467e8342d8796a01
Getting Private IP Address for Instance i-0467e8342d8796a01, please wait...
Private IP Address of i-0467e8342d8796a01 is 172.30.0.147

Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm1' (1) >

• • • Setup External EBS Volume for DBRoot #1 ***

• • • NOTE: You have the option to provide an
      existing EBS Volume ID or have a Volume created

Create a new EBS volume for DBRoot #1 ? [y,n] > n
Enter Volume ID for 'DBRoot1' () > vol-00854c297307deb39

STOPS HERE