[MCOL-2268] Amazon EC2 system- addModule is failing, incorrectly launching using the AMI Created: 2019-04-02 Updated: 2023-10-26 Resolved: 2020-04-15 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ? |
| Affects Version/s: | 1.2.2 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Critical |
| Reporter: | David Hill (Inactive) | Assignee: | Ben Thompson (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Environment: |
1um 2pm EC2 amazon system not using the AMI |
||
| Description |
|
Customer has a Amazon EC2 system that wasnt launched using the 1.2.2 AMI. It is configured to use the CLI API toolset. With this configuration, the addModule is launching the new instance usind the AMI, but the customer doesn't want this. It needs to launch using the instance that the customer has provided. The issue in the code is that when the postConfigure install is done and the user specifies the option to use the CLI API tool set, the code defaults to launching the AMI when add module is done. |
| Comments |
| Comment by John Dutchover [ 2019-04-02 ] |
|
CORRECTION/CLARIFICATION: |
| Comment by David Hill (Inactive) [ 2019-04-02 ] |
|
The code assumption is when this entry is setup amazon cloud, it works off the logic that the ami was used to launched the system and it will automatically add instances based on pm1 in the addModule logic. Customer needs to it add new UM2 on an already launched instance they have setup <Cloud>amazon-vpc</Cloud> |
| Comment by David Hill (Inactive) [ 2019-05-06 ] |
|
There are 2 issues here. First the setup. When installing on Amazon EC2 and you specify in postConfigure that you want to utilizing the CLI AMI's, that means that Columnstore can create instances and ebs for the user. Create instance can be done when user does addModule 2 issues. 1. Customer wanted to do addModule, buit wants to use their own Instances. They reported this didnt work. When they provided their instance id in the addModule, a new instance was launched instead of installing on their instance. I couldnt reproduce this. When I provided an instance, it would use that instance. For this needs to be tested to see if it works like it did for me or fails like it did for the customer. 2. Issue I found. When I did the first one successfully, used the already created instance. I then remove module that I just added and that instance got deleted. This shouldn't happen since it an instance that was already existed. So for this issue, the code or config needs to know its an instance that the customer create and then did addModule, and it shouldnt delete it when they removeModule. |
| Comment by Todd Stoffel (Inactive) [ 2020-04-15 ] |
|
OAM is being deprecated and replaced by an enhanced API and the MaxScale orchestration project. |