Ansible Tower Upgrade – Quick Note on EC2 Sizing
Last week I started on a personal project to get Ansible Tower upgraded in our lab. Our Tower deployment actually runs in AWS as an EC2 instance with some EBS backed storage. It's a simple and common setup for folks that are running Tower. There wasn't much excitement with this upgrade from 3.1 to 3.4 except for one minor hiccup.
We typically run lean and mean in the lab, using only what we really need to use resource-wise. The AWS instance for Tower is a m3.medium which gives a single vCPU and 3.75 GB of RAM. Ansible Tower requires 2 GB RAM minimum but has a recommended size of 4 GB RAM. Thus, the m3.medium seems to the most ideal EC2 instance type of this type of testing workload.
While the original 3.1 deployment had no issues with the m3.medium, the upgrade failed several times and quit reporting the following error:
TASK [preflight : Preflight check - Fail if this machine lacks sufficient...