-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provisioning over 50 Instances (F5 Workshop) causes Teardown to Fail. #1944
Comments
Actually, probably spoke too quickly...would need to revisit code and perhaps make some modifications, this PR was submitted a while back. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Summary
In the code you can provision 50+ labs however when doing a teardown of 50 or greater the teardown script will fail due to a limitation in AWS BOTO b/c it has a max limit of 200 Objects (In the F5 Labs case [50 x (2 Web Servers + 1 F5 BIG-IP + 1 Ansible Node)] + Control Node (201 Objects) this will cause the code to fundementally fail during the teardown process.
I have coded a way out of this issue which i have tested multiple times (50 Students) and this code deprovisions the lab appropriately and automatedly as the only way to get around this in the past was going into the AWS Console and manually deleting enough objects to allow the code to teardown (which isnt automated)
@heatmiser and i have had discussion on this and think its very important for RHDP and Anyone working with the code that provisions over 200 objects would need (feel free to adjust your number on this as i set to delete to 100 objects) to ensure plenty of space.
workshop/roles/manage_ec2_instances/tasks/teardown.yml
Code added at line 102 Before Install AWS CLI and after Debug all _workshop_vpc2_nodes
Issue Type
Bug
Extra vars file
Ansible Playbook Output
N/A at this time, but this is a known issue as BOTO has a 200 object limit
Ansible Version
Ansible Configuration
Ansible Execution Node
CLI Ansible (Ansible Core)
Operating System
The text was updated successfully, but these errors were encountered: