Open a-cesari opened 2 months ago
What is ami-0a946522147cbcbcc
? Is it one of the default Amazon Linux AMIs provided by Amazon? If not, could you try one of those, please?
Hi @nchammas , yes it's an official Amazon Linux 2 image
If you have an already know working combination of instance type and ami, I can try with them to check if it's a problem related to ami or instance type.
Hi @nchammas , yes it's an official Amazon Linux 2 image
Can you show me where exactly you are seeing that? I am not able to find mention of this AMI in the official listing from Amazon.
I just tried to launch, stop, and then start a cluster using ami-0588935a949f9ff17
and it worked fine for me.
Hi @nchammas , yes it's an official Amazon Linux 2 image
Can you show me where exactly you are seeing that? I am not able to find mention of this AMI in the official listing from Amazon.
I just tried to launch, stop, and then start a cluster using
ami-0588935a949f9ff17
and it worked fine for me.
I can only use amis in eu-central-1. And I can't find the one you are mentioning in eu-central-1 region. I now tried with this one (probably they also updated it during these days) but still same problem
I'm not sure where ami-0578f46b79ca9e3e7
is coming from, either. Please try an AMI returned by this list:
aws ec2 describe-images \
--region eu-central-1 \
--owners amazon \
--filters \
"Name=name,Values=amzn2-ami-hvm-*-gp2" \
"Name=root-device-type,Values=ebs" \
"Name=virtualization-type,Values=hvm" \
"Name=architecture,Values=x86_64" \
--query \
'reverse(sort_by(Images, &CreationDate))[:100].{CreationDate:CreationDate,ImageId:ImageId,Name:Name,Description:Description}'
Please also try a different instance type, like m6i.large
. Different instance types have different storage configurations. Flintrock is tested against a very small set of the possible storage configurations.
I'm not sure where
ami-0578f46b79ca9e3e7
is coming from, either. Please try an AMI returned by this list:aws ec2 describe-images \ --region eu-central-1 \ --owners amazon \ --filters \ "Name=name,Values=amzn2-ami-hvm-*-gp2" \ "Name=root-device-type,Values=ebs" \ "Name=virtualization-type,Values=hvm" \ "Name=architecture,Values=x86_64" \ --query \ 'reverse(sort_by(Images, &CreationDate))[:100].{CreationDate:CreationDate,ImageId:ImageId,Name:Name,Description:Description}'
Please also try a different instance type, like
m6i.large
. Different instance types have different storage configurations. Flintrock is tested against a very small set of the possible storage configurations.
Hi, thanks for the suggestion. Indeed it's a problem of finding the instance type. The following combos are now working in my case:
instance_type | ami | launch | destroy | restart (stop + start) |
---|---|---|---|---|
m6i.large | ami-0121de3d416d6f6a2 | yes | yes | yes |
m6i.large | ami-0578f46b79ca9e3e7 | yes | yes | yes |
m5.large | ami-0578f46b79ca9e3e7 | yes | yes | yes |
i4i.xlarge | ami-0578f46b79ca9e3e7 | yes | yes | NO |
It would be nice to understand what's the difference in storage config of the i4i. However not a big issue for me. I can use other instance types. Thanks a lot for the support. Feel free to close the issue if you wish.
Andrea
I will leave the issue open and re-title it to focus on this storage-related problem. Flintrock should handle it more gracefully, even if we don't support it.
Hi, I'm having issues when stopping and restarting the cluster. Stop is working fine (i.e. flintrock stop my-cluster). However when trying to start again (flintrock start my-cluster) the instances fails 1 of the 2 sanity checks, they cannot be reached event with console ssh login, and the cluster won't start. I'm guessing is something related to the ephemeral storage because (as you can see from the system log below) the instance is going in a "recovery mode" due to some errors related to ext4 partition non found
Do you have any guess? Thanks for your kind help. Andrea
Here a more complete log file. After you can find also my flintrock config.