search

chef-boneyard / chef-provisioning-aws

AWS driver and resources for Chef that uses the AWS SDK
Apache License 2.0
142 stars 122 forks source link

Tests in master branch failing #350

Open Fodoj opened 8 years ago

Fodoj commented 8 years ago

I've pulled master branch and run: AWS_TEST_DRIVER=aws chef exec bundle exec rspec spec. Bunch of specs failed. 

Finished in 9 minutes 4 seconds (files took 46.39 seconds to load)
134 examples, 11 failures, 3 pending

Failed examples:

rspec ./spec/integration/aws_cache_subnet_group_spec.rb:18 # Chef::Resource::AwsCacheSubnetGroup When the Chef server exists when the chef repo exists and with a VPC with an internet gateway and subnet aws_cache_subnet_group 'test-subnet-group' creates a cache subnet group
rspec ./spec/integration/aws_cloudsearch_domain_spec.rb:11 # Chef::Resource::AwsCloudsearchDomain When the Chef server exists when the chef repo exists and when connected to AWS aws_cloudsearch_domain 'test-1443614900298' creates a cloudsearch domain
rspec ./spec/integration/aws_cloudsearch_domain_spec.rb:19 # Chef::Resource::AwsCloudsearchDomain When the Chef server exists when the chef repo exists and when connected to AWS returns nil when aws_object is called for something that does not exist
rspec ./spec/integration/aws_s3_bucket_spec.rb:16 # Chef::Resource::AwsS3Bucket When the Chef server exists when the chef repo exists and when connected to AWS aws_s3_bucket 'chef_provisioning_test_bucket_e3c5ae39f8962276' creates a bucket
rspec ./spec/integration/aws_s3_bucket_spec.rb:22 # Chef::Resource::AwsS3Bucket When the Chef server exists when the chef repo exists and when connected to AWS creates aws_s3_bucket tags
rspec ./spec/integration/aws_s3_bucket_spec.rb:40 # Chef::Resource::AwsS3Bucket When the Chef server exists when the chef repo exists and when connected to AWS with existing tags updates aws_s3_bucket tags
rspec ./spec/integration/aws_s3_bucket_spec.rb:53 # Chef::Resource::AwsS3Bucket When the Chef server exists when the chef repo exists and when connected to AWS with existing tags removes all aws_s3_bucket tags
rspec ./spec/integration/aws_s3_bucket_spec.rb:77 # Chef::Resource::AwsS3Bucket When the Chef server exists when the chef repo exists and when a bucket with content exists aws_s3_bucket 'chef_provisioning_test_bucket_a6948a5db987576f' with recursive_delete set to true, deletes the bucket
rspec ./spec/integration/load_balancer_spec.rb:55 # Chef::Resource::LoadBalancer When the Chef server exists when the chef repo exists and with a VPC and a public subnet creates load_balancer tags
rspec ./spec/integration/load_balancer_spec.rb:75 # Chef::Resource::LoadBalancer When the Chef server exists when the chef repo exists and with a VPC and a public subnet with existing tags updates aws_load_balancer tags
rspec ./spec/integration/load_balancer_spec.rb:88 # Chef::Resource::LoadBalancer When the Chef server exists when the chef repo exists and with a VPC and a public subnet with existing tags removes all aws_load_balancer tags

Here is the full log of test run: https://gist.github.com/Fodoj/f99673bacec56cfbeb3b

tyler-ball commented 8 years ago
  1. User: arn:aws:iam::751747988410:user/kshirinkin is not authorized to perform: cloudsearch:DescribeDomains on resource: arn:aws:cloudsearch:eu-west-1:751747988410:domain/wont-exist - looks like you need the CloudSearch permissions added to your user. We also need to publish documentation for what credentials the test user needs (or we should have a before-all-tests block that runs and validates the necessary credentials are present.
  2. For the AWS::S3::Errors::InvalidBucketName error, will you try re-running against master? I was seeing that too and shortened the name in https://github.com/chef/chef-provisioning-aws/blob/master/spec/integration/aws_s3_bucket_spec.rb#L6
  3. For the Invalid Availability Zone: us-east-1d this is definitely a bug on my part. But does this error go away if you set AWS_TEST_DRIVER=aws::us-east-1?