Network interface is being doubled when async create VirtualMachine

[jkubrynski]

When I invoke createAsync() on the Azure.virtualMachines() definition it doubles the network interface setting. With normal create() it works OK.

"networkProfile": {
    "networkInterfaces": [
        {
            "id": "/subscriptions/XXXXXXX/resourceGroups/YYYY/providers/Microsoft.Network/networkInterfaces/ZZZZ",
            "properties": {
                "primary": true
            }
        },
        {
            "id": "/subscriptions/XXXXXXX/resourceGroups/YYYY/providers/Microsoft.Network/networkInterfaces/ZZZZ",
            "properties": {
                "primary": true
            }
        }
    ]
}

[martinsawicki]

odd that it's even possible...

[anuchandy]

@jkubrynski sorry for the delay in responding.

We had a rework in the underlying dependency graph in Dec 2016, in that work we tried to eliminate any race conditions in the core, adding duplicate entries to NIC array looks like a race condition.

But still i am trying to see this is reproducible, createAsync() of virtual machine return Observable<Indexable>, at some point of time consumer needs to subscribe to it - directly by calling Subscribe or indirectly by applying operators chain and calling Subscribe at the end of chain. Do you think you can share the code you use which shows how you subscribe and WAIT for operation to finish.

[martinsawicki]

closing due to inactivity/lack of repro/maybe already fixed