Volume not created

[brian...@gmail.com]

I tried rubber today but it failed to create the EBS volume. I ended up with just 8GB. What could have gone wrong?

image_id: ami-9abea4fb

hosts:

    web01:

        instance_roles: "web,app,db:primary=true"

        availability_zone: us-west-2a

        use_static_ip: true

        volumes:

          - size: 30

            zone: us-west-2a

            device: /dev/sdh

            mount: /ebs

            filesystem: ext4

            fog_options:

              type: gp2

[brian...@gmail.com]

  * 2016-01-19 00:09:14 executing `rubber:setup_volumes'

  * executing "echo $(ls /ebs/appdb-production 2> /dev/null)"

[Kevin Menard]

Hi Brian,

 

The log snippet doesn't really show that the EBS volume wasn't created. It's possible it mounted and the application just failed to deploy. Have you verified through the AWS console or by running "mount" on the remote machine that the volume indeed wasn't created and isn't mounted?

 

I'm going to look through some things on my end. The code for this hasn't changed in quite some time, but it's possible fog might have broken.

 

--

Kevin

--

You received this message because you are subscribed to the Google Groups "rubber" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rubber-ec2+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

 

[brian...@gmail.com]

I checked the AWS console. The EBS volume for 30GB was not created. All that was created was 8GB for the OS.

[Kevin Menard]

Thanks for reporting. I'll take a look. I suspect the issue may be the use of t2.micros. IIRC, they can only be deployed in a VPC and we didn't have support for that until the 3.2.0 release. Please note that the default behavior is to be backwards-compatible with previous rubber.yml files. If you don't generate a new one or add the config for using VPC, you'll continue to deploy into either an EC2 Classic or auto-VPC environment.

 

--

Kevin