1.0.4-1 AMI postConfigure failed to install for multi-server configuration

Build tested: 1.0.4-1 AMI

I created an instance using the AMI and ran postConfigure attempting to setup a 1UM2PM stack. The option that I choose was to let postConfigure to create the needed instances and external storage EBSs. At the point of creating the EBS for PM1, I encountered an error:
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] > y
Create AWS Volume for DBRoot #1
Formatting DBRoot #1, please wait...

• • • • addDbroot Failed: API Failure return in addDbroot API

postConfigure aborted.

I repeated the postConfigure. This time, dbroot already has a default volume ID and did not need to create one. postConfigure continue onto PM2 installation and hit the same error. Repeating postConfigure led to the completion of installation on all servers.

When attempting to startup the stack, the process got stuck and the stack did not come up. I noticed procmon on PM2 did not start. I shut down the system and attempted to start it again and that did not help. I noticed that PM1's /etc/fstab file has mount commands for both dbroots and PM2/s /etc/fstab did not have any.

/dev/xvdg /usr/local/mariadb/columnstore/data1 ext2 noatime,nodiratime,noauto 0 0
/dev/xvdh /usr/local/mariadb/columnstore/data2 ext2 noatime,nodiratime,noauto 0 0

I moved the mount commands for dbroot2 from PM1 to PM2 and was able to start the system up.

After the system started up, there was not system catalog. I had to run the "rebuilder 7" command manually to have system catalog created and the stack was operational since.