I seem to be having some serious issues getting the vagrant-aws plugin to work. Thus far, it's never got past attempting to call describe_security_groups:
==> mgmt: -- VPC tenancy specification: default
/home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/expects.rb:7:in `response_call': InvalidParameterValue => Value (20161213T101928Z) for parameter Timestamp is invalid. Must be in ISO8601 format. (Fog::Compute::AWS::Error)
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/response_parser.rb:9:in `response_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:388:in `response'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:252:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/idempotent.rb:27:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:272:in `rescue in request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:215:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/idempotent.rb:27:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:272:in `rescue in request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:215:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/idempotent.rb:27:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:272:in `rescue in request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:215:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-xml-0.1.2/lib/fog/xml/sax_parser_connection.rb:35:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-xml-0.1.2/lib/fog/xml/connection.rb:7:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-aws-1.0.0/lib/fog/aws/compute.rb:527:in `_request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-aws-1.0.0/lib/fog/aws/compute.rb:522:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-aws-1.0.0/lib/fog/aws/requests/compute/describe_security_groups.rb:38:in `describe_security_groups'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-aws-1.0.0/lib/fog/aws/models/compute/security_groups.rb:63:in `all'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:229:in `block in allows_ssh_port?'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:228:in `map'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:228:in `allows_ssh_port?'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:106:in `call'
Why the AWS endpoint isn't accepting that perfectly valid ios8601 date as iso8601 formatted I don't know, but when I alter fog's time.rb to generate a different iso8601 variation (%Y-%m-%dT%H:%M%SZ), I instead get this:
==> mgmt: Launching an instance with the following settings...
==> mgmt: -- Type: t2.small
==> mgmt: -- AMI: <elided>
==> mgmt: -- Region: eu-west-1
==> mgmt: -- Keypair: charlescooke
==> mgmt: -- Subnet ID: <elided>
==> mgmt: -- Private IP: <elided>
==> mgmt: -- Security Groups: ["vagrant-qa-base"]
==> mgmt: -- Block Device Mapping: [{"DeviceName"=>"/dev/sda1", "Ebs.VolumeSize"=>16}]
==> mgmt: -- Terminate On Shutdown: false
==> mgmt: -- Monitoring: false
==> mgmt: -- EBS optimized: false
==> mgmt: -- Source Destination check:
==> mgmt: -- Assigning a public IP address in a VPC: false
==> mgmt: -- VPC tenancy specification: default
/home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/expects.rb:7:in `response_call': InvalidAction => The action urn:Post is not valid for this web service. (Fog::Compute::AWS::Error)
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/response_parser.rb:9:in `response_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:388:in `response'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:252:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/idempotent.rb:27:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:272:in `rescue in request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:215:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/idempotent.rb:27:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:272:in `rescue in request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:215:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/idempotent.rb:27:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/middlewares/base.rb:11:in `error_call'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:272:in `rescue in request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/excon-0.54.0/lib/excon/connection.rb:215:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-xml-0.1.2/lib/fog/xml/sax_parser_connection.rb:35:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-xml-0.1.2/lib/fog/xml/connection.rb:7:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-aws-1.0.0/lib/fog/aws/compute.rb:527:in `_request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-aws-1.0.0/lib/fog/aws/compute.rb:522:in `request'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-aws-1.0.0/lib/fog/aws/requests/compute/describe_security_groups.rb:38:in `describe_security_groups'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/fog-aws-1.0.0/lib/fog/aws/models/compute/security_groups.rb:63:in `all'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:229:in `block in allows_ssh_port?'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:228:in `map'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:228:in `allows_ssh_port?'
from /home/charlescooke/.vagrant.d/gems/2.2.5/gems/vagrant-aws-0.7.2/lib/vagrant-aws/action/run_instance.rb:106:in `call'
I seem to be having some serious issues getting the vagrant-aws plugin to work. Thus far, it's never got past attempting to call describe_security_groups:
Why the AWS endpoint isn't accepting that perfectly valid ios8601 date as iso8601 formatted I don't know, but when I alter fog's time.rb to generate a different iso8601 variation (%Y-%m-%dT%H:%M%SZ), I instead get this:
Any ideas?