I just changed the Azure provider (locally) to allocate a virtual network
using a Location instead of Affinity Group, and it got most of the way
through bootstrap. It ends up failing with
    "2014-10-21 01:43:39 ERROR juju.cmd supercommand.go:323 Get
https://management.core.windows.net/6f0e3b87-f601-40fd-9727-76d05563fedd/services/hostedservices:
dial tcp: lookup management.core.windows.net: No address associated with
hostname"

I'm not sure if we can or should change the code, as in the past I've
observed problems when using Location and not Affinity Group.

Cheers,
Andrew

diff --git a/provider/azure/environ.go b/provider/azure/environ.go
index 9d5d5bf..b435b95 100644
--- a/provider/azure/environ.go
+++ b/provider/azure/environ.go
@@ -201,8 +201,8 @@ func (env *azureEnviron) createVirtualNetwork() error {
        }
        defer env.releaseManagementAPI(azure)
        virtualNetwork := gwacl.VirtualNetworkSite{
-               Name:          vnetName,
-               AffinityGroup: env.getAffinityGroupName(),
+               Name:     vnetName,
+               Location: env.getSnapshot().ecfg.location(),
                AddressSpacePrefixes: []string{
                        networkDefinition,
                },


On Tue, Oct 21, 2014 at 5:13 AM, Kapil Thangavelu <
kapil.thangav...@canonical.com> wrote:

>
> possibly related to http://azure.microsoft.com/en-us/status/
>
> "Starting at approximately 19:00 on the 18th Oct, 2014 UTC a limited
> subset of customers may experience intermittent errors when attempting to
> access Azure Virtual Networks. Engineers are continuing with their manual
> recovery and have validated significant improvement as a result of their
> action plan. Customers may begin to see improvements to availability of
> their Virtual Networks. The next update will be provided in 2 hours or as
> events warrant."
>
> -k
>
>
> On Mon, Oct 20, 2014 at 5:05 PM, Nate Finch <nate.fi...@canonical.com>
> wrote:
>
>> This is a pretty major problem.... it *seems* like it must be Azure's
>> fault, but it would be good to get more information about it.  If anyone
>> cares to investigate, here's the bug:
>>
>> https://launchpad.net/bugs/1383310
>>
>>
>> --
>> Juju-dev mailing list
>> Juju-dev@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>>
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Reply via email to