Puppet » Cloud-Provisioner

It looks like the subnet ID needed for VPC was added in https://github.com/puppetlabs/puppetlabs-cloud-provisioner/commit/f11774e647d4b9b4bf0f058b127a8001c41d9cd3 but it looks like group ID is not being properly set:

VPC subnet is now working, but the security group is not. Using the group ID produces an error:

# puppet node_aws create --image=ami \ 
> --group=group-id \ 
> --keyname=mykey \ 
> --subnet=subnet-id \ 
> --type=m1.small 
err: Unrecognized security groups: group-id
err: Try 'puppet help node_aws create' for usage

Using the group name results in setting the default group and not the one specified: 
# puppet node_aws create --image=ami \ 
> --group=mygroup \ 
> --keyname=mykey \ 
> --subnet=subnet-id \ 
> --type=m1.small \ 
notice: Creating new instance ... 
... 
notice: Server instance-id public dns name:

Bump.

What’s the decision that needs to be made? Does Nigel still need to make it?

-Jeff

The decision was “will we devote some time to fixing this bug”. It’s probably more a Josh question than a Nigel one now.

I understand that this is fixed in newer versions of Fog.

FWIW – I just tested this with fog v1.4.0 and I am getting the same behaviour as James.

I just tested with PE 2.6.1 (fog 1.5.0) and I still see this problem.