While attempting to use the `puppetlabs-aws` module I keep experiencing the error in the subject.
My manifest:
ec2_instance { 'puppet_prov_test':
ensure => 'present',
availability_zone => 'us-east-1a',
image_id => 'ami-61bbf104',
instance_type => 't2.micro',
key_name => 'PUPPETMASTER-2',
region => 'us-east-1',
subnet => 'subnet-ff5bc992',
security_groups => ['PPL'],
}
The full `puppet apply` output:
# puppet apply --verbose /etc/puppetlabs/code/environments/production/modules/aws_prod/manifests/init.pp
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Info: Loading facts
Notice: Compiled catalog for puppetmaster.cspops.int in environment production in 0.07 seconds
Info: Applying configuration version '1457071103'
Info: Checking if instance puppet_prov_test is running in region us-east-1
Info: Checking if instance puppet_prov_test is stopped in region us-east-1
Info: Starting instance puppet_prov_test in region us-east-1
Error: Security groups 'PPL' not found in VPCs 'vpc-e05bc98d'
Error: /Stage[main]/Main/Ec2_instance[puppet_prov_test]/ensure: change from absent to present failed: Security groups 'PPL' not found in VPCs 'vpc-e05bc98d'
Notice: Applied catalog in 10.45 seconds
It seems like it would be a very straight forward solution: Make sure the PPL security group is in the VPC. Unfortunately, while obvious, it isn't exactly correct:
As evidenced, the VPC ID is exactly the one being reported as not having it.
The user account I'm working with is part of our admin group so I know it has all the necessary permissions.
What could be causing this inaccurate report?
↧
