Azure RM creates templates with VMs in 2 availability sets but does not specify the primaryAvailabilitySetName

[nithril]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Two availability set (AVS) are used for the Azure ARM contrib/azurerm/roles/generate-templates/defaults/main.yml

availabilitySetMasters: "master-avs" 
availabilitySetMinions: "minion-avs"

According to the documentation when multiple AVS are used, the config primaryAvailabilitySetName must be set which is not the case in roles/kubernetes/node/templates/azure-cloud-config.j2. Then when k8s creates the Azure LB, it cannot add the nodes to the LB.

Environment:

• Cloud provider or hardware configuration:
  Azure

Kubespray version (commit) (git rev-parse --short HEAD):
8b3ce6e. I have not test with the HEAD but the template are the same.

Thank you.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.