This message was deleted.
# ask-for-helps
Slackbot
11/10/2022, 6:02 PMThis message was deleted.
b
Bo
11/10/2022, 6:23 PM@rekil You should able to use
terraform destroyr
rekil
11/10/2022, 6:27 PMthank you very much will try that , after that i should generate the terraform with -
bentoctl generate -f deployment_config.yamlb
Bo
11/10/2022, 6:27 PMyep
r
rekil
11/10/2022, 6:28 PMthanks i'll try and report back
rekil
11/10/2022, 6:30 PMsorry but what do i put in here
b
Bo
11/10/2022, 6:35 PMyou could use
terraform destroy -var-file bentoctl.tfvarsπ 1
r
rekil
11/10/2022, 6:38 PMok successfully deleted, let me rerun the other commands
rekil
11/10/2022, 6:44 PMhmm back to the same error :
Copy code
β·
β Error: creating IAM instance profile stable-diffusion-bentoml-instance-profile: EntityAlreadyExists: Instance Profile stable-diffusion-bentoml-instance-profile already exists.
β status code: 409, request id: be742c25-c728-42fc-8e8f-bcc78863894f
β
β with aws_iam_instance_profile.ip,
β on <http://main.tf|main.tf> line 90, in resource "aws_iam_instance_profile" "ip":
β 90: resource "aws_iam_instance_profile" "ip" {
β
β΅
β·
β Error: creating Security Group (stable-diffusion-bentoml-bentoml-sg): InvalidGroup.Duplicate: The security group 'stable-diffusion-bentoml-bentoml-sg' already exists for VPC 'vpc-a96110d1'
β status code: 400, request id: 724408a5-52c5-44b5-a914-26dc31064575
β
β with aws_security_group.allow_bentoml,
β on <http://main.tf|main.tf> line 96, in resource "aws_security_group" "allow_bentoml":
β 96: resource "aws_security_group" "allow_bentoml" {
β
β΅b
Bo
11/10/2022, 6:44 PMhmmm
Bo
11/10/2022, 6:44 PMthose should deleted by terraform
Bo
11/10/2022, 6:44 PMcan you manually delete them and try again?
Bo
11/10/2022, 6:45 PMalso have to hop on a call for 20 mins to debug
r
rekil
11/10/2022, 6:46 PMok thank you, i can try and get back
rekil
11/10/2022, 7:10 PMso managed to delete those but i'm back to the vCPU limit error, i feel i'm missing something very basic:
Copy code
β·
β Error: creating EC2 Instance: VcpuLimitExceeded: You have requested more vCPU capacity than your current vCPU limit of 32 allows for the instance bucket that the specified instance type belongs to. Please visit <http://aws.amazon.com/contact-us/ec2-request> to request an adjustment to this limit.
β status code: 400, request id: 50a70b98-b99a-4103-84c1-8e40a8e13a8e
β
β with aws_instance.app_server,
β on <http://main.tf|main.tf> line 141, in resource "aws_instance" "app_server":
β 141: resource "aws_instance" "app_server" {s
Sean
11/12/2022, 10:48 AMWhat size of
g4dnxlarge2xlargeSean
11/12/2022, 10:49 AMDo you have any existing allocated nodes of
g4dnSean
11/16/2022, 4:11 AM@rekil any update here?
r
rekil
11/16/2022, 4:58 AM@Sean i tried on xlarge, 2xlarge andd 4xlarge.
rekil
11/16/2022, 4:58 AMbut it's giving the vCPU limit error.
s
Sean
11/16/2022, 4:59 AMDo you have any existing running instances of GPU nodes in the region?
r
rekil
11/16/2022, 5:01 AMi ssh into that machine and follow the instructions on the github page. I feel i'm missing something obvious
s
Sean
11/16/2022, 5:04 AMThis error is thrown from AWS when running terraform against the EC2 provider. EC2 instance cannot be allocated due to exceeding vCPU quota. A single
g4dn.xlargeSean
11/16/2022, 5:05 AMHave you tried requesting a
g4dn.xlarger
rekil
11/16/2022, 5:15 PMSo we increased the vCPU limit to 32 and tried with a g4dn.2xlarge but still got the same error on limits. Is there someway to set up a call to run through this error, just to make sure i'm not missing something very obvious