juju bootstrap fails in Azure (BadRequest - The affinity group name is empty or was not specified.)

[Max Cantor]

This is not a repeat of #1236136, I am attempting to launch instances in the same region as my storage instance. Tried both East US and West US.

Debug output:

http://pastebin.com/AQArivJz

[Curtis Hovey (sinzui)]

This may be a duplicate of bug 1236136

[Curtis Hovey (sinzui)]

Is your "storage-account-name" in the same "location". In early testing, I found I could only bootstrap azure using US West (where the tools were first released tools-url: https://jujutools.blob.core.windows.net/juju-tools/tools) and my storage-account-name had to also be in US West. I can see from the log that Juju search many places for tools, and ultimately selected the location we released tools too, but from my experience, they will only be installed if your location is US West and storage-account-name is also in US West.

[Max Cantor (max-a)]

It is in the same location and it's not a duplicate of the other bug.

Thanks though.

On Tuesday, December 10, 2013, Curtis Hovey wrote:

> Is your "storage-account-name" in the same "location". In early testing,
> I found I could only bootstrap azure using US West (where the tools were
> first released tools-url: https://jujutools.blob.core.windows.net/juju-
> tools/tools) and my storage-account-name had to also be in US West. I
> can see from the log that Juju search many places for tools, and
> ultimately selected the location we released tools too, but from my
> experience, they will only be installed if your location is US West and
> storage-account-name is also in US West.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1259350
>
> Title:
> juju bootstrap fails in Azure (BadRequest - The affinity group name is
> empty or was not specified.)
>
> Status in juju-core:
> Triaged
>
> Bug description:
> This is not a repeat of #1236136, I am attempting to launch instances
> in the same region as my storage instance. Tried both East US and
> West US.
>
> Debug output:
>
> http://pastebin.com/AQArivJz
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1259350/+subscriptions
>

--

Max Cantor
*docmunch.com <http://docmunch.com>* - data-driven document management
<email address hidden>
[phone]
[phone]x702

[Andrew Wilkins (axwalk)]

I think I have just reproduced this (at least, I get the same error message, and it's not related to region). Seems to happen if the affinity group already exists. Bootstrap then attempts to delete the affinity group, but this will fail if there's something still referencing it.

Check your Azure console to see if there are any juju-related things hanging around.

[Richard Harding (rharding)]

I got this in an environment gone south. Destroy environment --force did not clear out the affinity group or the storage container. The container won't be removed manually:

Storage account jujuguieast0 has container(s) which have an active image and/or disk artifacts. Ensure those artifacts are removed from the image repository before deleting this storage account.

This is with no virtual machines in existence. I ended up renaming my environment name and creating a new/different storage container and worked around the old data that I can't remove.

[Andrew Wilkins (axwalk)]

We now allow for the affinity group to exist when bootstrapping. Closing - please reopen if you're able to reproduce this after 1.19.4 is out.