Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

Does not seem to respect affinity-group-name parameter #30

Open
andersosthus opened this issue Jul 18, 2014 · 2 comments
Open

Does not seem to respect affinity-group-name parameter #30

andersosthus opened this issue Jul 18, 2014 · 2 comments

Comments

@andersosthus
Copy link

Hi,

Trying to provision a VM into a Affinity group using --affinity-group-name='my-affinity-group' throws an error:

BadRequest : The affinity group name is empty or was not specified.

I've verified that I got the right name, and that the affinity group exists on the correct account.

Is this a known thing, or might I be doing something wrong. I've pasted the full command here, just in case:

puppet azure_vm create --management-certificate="my.pfx"  --azure-subscription-id="my-sub-guid" --image="b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04-LTS-amd64-server-20140618.1-en-us-30GB" --location='north europe' --vm-name='my-vm' --vm-user='myuser' --puppet-master-ip='my-puppet-master' --virtual-network-name='my-vnet' --virtual-network-subnet='my-subnet' --cloud-service-name='my-cs' --affinity-group-name='my-ag'
@ranjan
Copy link
Contributor

ranjan commented Jul 21, 2014

This bug recently introduce due to recent changes in virtual network API. Next release will fix this issue. You won't get this issue when you create virtual network using puppet azure_vnet command and use the same virtual network to provision the virtual machine

@bwodicka
Copy link

bwodicka commented Nov 3, 2014

Is there a current workaround for this? What about if I have a VNET that doesn't use an affinity group (i.e. the Regional VNET)?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants